[TRNSYS-users] Fail rebuilding Trnsys

[Diego A. Arias]

Dear Guillermo,

It is possible that you have two types that are called Type200.  Please 
look in the source code of these types for these lines:
SUBROUTINE TYPE200(TIME,XIN,OUT,T,DTDT,PAR,INFO,ICNTRL,*)
!DEC$ATTRIBUTES DLLEXPORT :: TYPE200
I guess that your routine Type141 does not have these lines with the 
corresponding number 141.
Please let me know if this helps.
Best regards,

Diego

Guillermo Enrique Cabral wrote:
> Hello! I create a new type that call another type. The problem is that when 
> rebuild Trnsys I get the next error mesage:
>
> DUMF40.LIB(DUM200.OBJ) : error LNK2005: _TYPE200 already defined in 
> TYPE200.OBJ 
> DUMF40.LIB(DUM200.OBJ) : warning LNK4006: _TYPE200 already defined in 
> TYPE200.OB 
> J; second definition ignored 
>    Creating library \trnwin\TRNLIB32.lib and object \trnwin\TRNLIB32.exp 
> TYPE200.OBJ : error LNK2001: unresolved external symbol _TYPE141 at 28 
> \trnwin\TRNLIB32.DLL : fatal error LNK1120: 1 unresolved externals 
>  
> ??????????????????????????????????????????????????????????????? 
> ?           TRNSYS Executable File is up to date!             ? 
> ??????????????????????????????????????????????????????????????? 
> Presione una tecla para continuar . . . 
>
>
>
> TYPE200 is the module that I create and TYPE141 is the module that is being 
> called from TYPE200. I wish to know if it can be done in this way and what I 
> can do to solve this.
>
> Guillermo Cabral
> _______________________________________________
> TRNSYS-users mailing list
> TRNSYS-users at engr.wisc.edu
> https://www.cae.wisc.edu/mailman/listinfo/trnsys-users
>   


-- 

Diego A. Arias
TRNSYS Coordinator
Solar Energy Laboratory
University of Wisconsin - Madison
1500 Engineering Drive
Madison, WI 53706