Re: [certi-dev] CERTI Windows build

[Jean-Philippe Lebel]

Your patch works like a charm. I was able to build librti1516 and 
libfedtime1516 without any error or warning. I was also able to build a 
simple app with the generated libraries.

Eric, may I suggest that you test the patch on linux and, if successful, 
that you commit the patch?

From my point of view the solution is simple and elegant.

JPL

On 28/09/2011 9:49 AM, Jan-Patrick Osterloh wrote:
> Hi JPL,
>
> --- Quoted from Jean-Philippe Lebel (Date: 28.09.2011 14:54): ---
> > 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.
> Ok, I see that. But then I wonder on #3:
>
> > I've suggested that we use #3 but that we do not export symbol of
> >      VariableLengthData from either libfedtime1516 or librti1516.
> Isn't that then the same problem, if neither libfedtime1516 nor
> librti1516 export the VariableLengthData? I think one of them has to
> export the symbols.
>
> So, let's say libRTI1516 exports VariableLengthData, and libfedtime1516
> not. Then we just have to ensure, that fedtime can be build. For this,
> we could use the static library. I tried this, and for me it worked well
> on mingw. I attached my patch. Maybe you can test this with VS? If it
> works for you too, then Eric could check it on Unix.
>
>
> > The
> >      circular dependencies is present in both Pitch and Mak
> >      implementation...
>   How are they solving the problem? I couldn't see how to do it in an
> other way, because as I read in the cmake documentation, circular
> dependencies work only, when both libraries are static libraries, but
> this is probably not what we wan't? Ok, I'm not that big expert with
> cmake, etc., maybe you have a better solution.
>
> JPO


--
Jean-Philippe Lebel, ing., MBA
ForwardSim inc.
Tel.: 418-650-3493 ext 6001
Fax.: 418-650-5661