Re: [certi-dev] CERTI Windows build

[Jean-Philippe Lebel]

Doing so would result, on Windows at least, on the VarData1516 not being
exported at all, thus resulting in a bunch of unresolved external when
linking with an app that uses Certi. I don't know I that could work on
mingw.

JPL

-----Original Message-----
From: address@hidden
[mailto:address@hidden On Behalf Of
Jan-Patrick Osterloh
Sent: 28 septembre 2011 07:53
To: CERTI development discussions
Subject: Re: [certi-dev] CERTI Windows build

Hi all,

--- Quoted from Eric Noulard (Date: 27.09.2011 20:02): ---
>
>> I've tested #1  but symbols from the newly created static lib are not 
>> exported and a far as I know, there is no solution to that problem on 
>> Windows.
>>
>> And a dynamic library? For mingw it worked well. I attached the patch 
>> from Christoph to show you what he did.
>>
>> Would badly break the standard.
> We should really try to avoid that.

But a static library (VarData1516.a) would be ok? I.e. building the
VarData1516 objects, making a static library from it, and link RTI1516 and
FedTime1516 against this?

JPO



--
Dipl. Inform. Jan-Patrick Osterloh
FuE Bereich Verkehr | R&D Division Transportation Human Centered Design
Group

OFFIS
FuE Bereich Verkehr | R&D Division Transport Escherweg 2 - 26121 Oldenburg -
Germany
Phone/Fax: +49 441 97 22-524/502
E-Mail: address@hidden
URL: http://www.offis.de