[TRNSYS-users] Accessing subroutines embedded in other private Types

[David BRADLEY]

Antoine,
   The simplest approach may be for your colleagues at the other company 
to create a DLL containing their Types. Since their Types would be 
exported in the same way as any other TRNSYS Type, their DLL and the 
Types contained in it would be loaded by the TRNSYS kernel. Your Types 
could then access theirs.
Best,
  David


On 12/19/2012 10:50, Antoine Gautier wrote:
>
> Dear users
>
> I work hand in hand with another company and share a lot of private 
> Trnsys Types with them (including source codes).
>
> I would like to easily access their subroutines from my own Types 
> without having to include all their Types in my IVF project. In other 
> words I want to reproduce the same capability that I have with generic 
> Trnsys functions through the TRNDll.lib library.
>
> What I have already tried in vain.
>
> ·Include their library *.lib (automatically generated in the Release 
> directory) in the Libraries folder of my IVF project
>
> ·Specify the path to their Release directory in my IVF project 
> configuration (Fortran/General/Additional Include Directories)
>
> Nota: I use IvfCXE2013.
>
> Does anybody have a clue on how to do it?
>
> Thanks a lot and merry Christmas
>
> --
>
> Antoine Gautier
> SolamenSAS
> +33 6 58 24 02 60
>
> antoine.gautier at solamen.fr <mailto:antoine.gautier at solamen.fr>
>
>
>
> _______________________________________________
> TRNSYS-users mailing list
> TRNSYS-users at cae.wisc.edu
> https://mailman.cae.wisc.edu/listinfo/trnsys-users

-- 
***************************
David BRADLEY
Principal
Thermal Energy Systems Specialists, LLC
22 North Carroll Street - suite 370
Madison, WI  53703 USA

P:+1.608.274.2577
F:+1.608.278.1475
d.bradley at tess-inc.com

http://www.tess-inc.com
http://www.trnsys.com

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.onebuilding.org/pipermail/trnsys-users-onebuilding.org/attachments/20121219/c52fd208/attachment-0005.htm>