Re: [TRNSYS-users] how to make Trnsys read...

["mk23\@inwind\.it" <mk23@xxxxxxxxx>]

hi to all.

we followed Michael's suggestions but probaly we skipped some steps again in building a new TRNlib.dll

> I think you may be skipping the link process. After all Types and kernel 
> routines are compiled into .obj files, 

ONE BY ONE?!!! we didn't find any "compile all" command or similar...

> they need to be linked together 
> to form a DLL (TRNDll.dll in TRNSYS 16, TRNLib.dll in TRNSYS 15). If you 
> are using the CVF compiler the easier way is to use the workspace 
> included in the distribution and rebuild the DLL (F7).

after compiling the type 36 we modified (from the CVF).  we selected "rebuild all" command but a message like below came out. It is the same song if doing it from another type...
It seems not finding the kernal routines, but nothing change even putting types and kernel routines file together in the same folder...

here the errors message:

Deleting intermediate files and output files for project 'Type36 - Win32 Debug'.
--------------------Configuration: Type36 - Win32 Debug--------------------
Compiling Fortran...
C:\trnsys15\Types\Type36.for
Linking...
Type36.obj : error LNK2001: unresolved external symbol _LINKCK@24
Type36.obj : error LNK2001: unresolved external symbol _TALF@24
Type36.obj : error LNK2001: unresolved external symbol _TYPECK@20
Type36.obj : error LNK2001: unresolved external symbol _RCHECK@20
dfor.lib(DFORMAIN.OBJ) : error LNK2001: unresolved external symbol _MAIN__
Debug/Type36.exe : fatal error LNK1120: 5 unresolved externals
Error executing link.exe.

Type36.exe - 6 error(s), 0 warning(s)

HOW TO LINK KERNAL ROUTINES AND TYPES? IT DOESN'T SEEM TO BE AUTOMATIC WITH THE REBUILD ALL COMMAND...

we now me are messing up our life and the trnsys version installed here...be patient!...

Pietro and Michele




> Pietro,
> > together with a collegue we modified type 36 and we compiled it. we 
> > susptituted its compiled files in the folder TYPES but trnsys engine 
> > seems no to read the new files. We know we are wrong but we don't know 
> > where...
> 
> I think you may be skipping the link process. After all Types and kernel 
> routines are compiled into .obj files, they need to be linked together 
> to form a DLL (TRNDll.dll in TRNSYS 16, TRNLib.dll in TRNSYS 15). If you 
> are using the CVF compiler the easier way is to use the workspace 
> included in the distribution and rebuild the DLL (F7). The time stamp of 
> the DLL should have changed after that.
> 
> Also, please note that if you use TRNSYS 16, it may be safer and more 
> convenient in the long run to create a modified copy of Type 36 (say 
> Type 236) which you would compile into a separate DLL. This will make it 
> easier for you to share the Type with other users and it will also make 
> TRNSYS updates easier to apply.
> Volume 8 of the documentation has instructions to create a new component 
> and compile it into an external DLL.
> 
> Kind regards,
> 
> Michaël Kummert
> 
> -- 
> _________________________________________________________
> 
> Michaël Kummert
> 
> Solar Energy Laboratory - University of Wisconsin-Madison
> 1303 Engr Res Bldg, 1500 Engineering Drive
> Madison, WI 53706
> 
> Tel: +1 (608) 263-1589
> Fax: +1 (608) 262-8464
> E-mail: kummert@xxxxxxxxxxxxx
> 
> SEL Web Site: http://sel.me.wisc.edu
> TRNSYS Web Site: http://sel.me.wisc.edu/trnsys
> _______________________________________________
> TRNSYS-users mailing list
> TRNSYS-users@xxxxxxxxxxxxx
> https://www.cae.wisc.edu/mailman/listinfo/trnsys-users
> 




____________________________________________________________
Navighi a 2 MEGA e i primi 3 mesi sono GRATIS. 
Scegli Libero Adsl Flat senza limiti su http://www.libero.it



_______________________________________________
TRNSYS-users mailing list
TRNSYS-users@xxxxxxxxxxxxx
https://www.cae.wisc.edu/mailman/listinfo/trnsys-users