[TRNSYS-users] TRNSYS 17 build - Intel Visual Fortran & Microsoft Visual Studio

[Briana Paige Kemery]

Michaël, David, Marion,

I was indeed able to compile without errors once I commented out line 50 of
callprogram.

Fortunately (or unfortunately depending on how you look at it), I'm using
Harmonizer, so I won't have any problems if Fluent or Type 56 are affected
by the change but it's good to know for future reference.

Thanks to all of you for your prompt assistance.
Briana

Briana Paige Kemery, BEng, EIT

*sustainable building energy systems*

 briana.paige at sbes.ca
 +1 613 795 1432
​​
<https://twitter.com/brianapaige> @SBES_group
<https://twitter.com/SBES_group>
 sbes.ca


On 3 June 2014 05:01, Marion Hiller <Hiller at transsolar.com> wrote:

>   David and Briana,
>
>
>
> Type 56 also uses callprogram. J
>
> However, I commented out the line 50 and everything is running fine.
>
>
>
> For building simulation with type56 you can check this by the date of the
> *.inf  file.
>
> This file should be generated before each simulation.
>
>
>
> Marion
>
>
>  ------------------------------
>
> *Von:* trnsys-users-bounces at cae.wisc.edu [mailto:trnsys-users-
> bounces at cae.wisc.edu] *Im Auftrag von *David BRADLEY
> *Gesendet:* Montag, 2. Juni 2014 21:44
> *An:* TRNSYS users mailing list at the Solar Energy Lab, UW-Madison;
> briana.paige at sbes.ca
> *Betreff:* Re: [TRNSYS-users] TRNSYS 17 build - Intel Visual Fortran &
> Microsoft Visual Studio
>
>
>
> Briana,
>   I'm afraid I don't have that version of the compiler and it sounds as
> though there has been a slight change that will require a change in
> callprogram. Michaël is quite correct that callprogram is only used by a
> few standard components (Type101 (calling fluent) and Type66 (calling
> EES)). You can either comment out the offending line or you can simply
> exclude Type101, Type66 and callprogram from the project when you rebuild
> it.
> Kind regards,
>  David
>
>
> On 6/2/2014 12:41, Briana Paige Kemery wrote:
>
>  Hi,
>
>
>
> I need to create my own type and this is what I'm using:
>
>
>
>  OS: Windows 8.1 Pro
>
>  TRNSYS version: 17.01.0025
>
>  Microsoft Visual Studio: Version 12.0.30501.00 Update 2
>
> Intel Visual Fortran Composer XE 2013 SP1: Package ID:
> w_fcompxe_2013_sp1.3.202
>
>
>
> I opened:
>
>
>
>  C:\Trnsys17\Compilers\Ivf11x\lvf11x.sln
>
>
>
> in VS and tried to build the release version of the solution. Even before
> compiling with the type I'm creating, I get the 2 fatal errors and the
> build is aborted. This is the build output for TRNSYS 17 without any added
> types:
>
>
>
>  2>Callprogram.f90
>
> 2>C:\Trnsys17\SourceCode\Kernel\Callprogram.f90(50): error #6580: Name in
> only-list does not exist.   [CREATEPROCESS]
>
> 2>compilation aborted for C:\Trnsys17\SourceCode\Kernel\Callprogram.f90
> (code 1)
>
>
>
> Line 50 in Callprogram.f90 where the error is thrown:
>
>
>
>  50    Use ifport , only:createProcess
>
>
>
> Maybe I'm missing something or there's a compatibility problem between
> TRNSYS and the Fortran compiler? I'd appreciate any insight on this problem.
>
>
>
> Thanks,
>
> Briana
>
>
>
> Sustainable Building Energy Systems
>
> briana.paige at sbes.ca
>
>
>
>
>   _______________________________________________
>
> 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/20140603/897875bd/attachment-0001.htm>