[prev in list] [next in list] [prev in thread] [next in thread] 

List:       flightgear-devel
Subject:    Re: [Flightgear-devel] Use of EXPORT in CMake
From:       Saikrishna Arcot <saiarcot895 () gmail ! com>
Date:       2013-10-17 23:47:37
Message-ID: 52607719.90609 () gmail ! com
[Download RAW message or body]

Correction: that should be 2.8.10, not 2.10.

Saikrishna Arcot

On Thu 17 Oct 2013 07:29:11 PM EDT, Saikrishna Arcot wrote:
> I was thinking something similar to this:
>
> |if(${CMAKE_VERSION} VERSION_LESS 2.10)||
> ||  // old method, which I think was just install||
> ||else(${CMAKE_VERSION} VERSION_LESS 2.10)||
> ||  // new EXPORT method||
> ||endif(${CMAKE_VERSION} VERSION_LESS 2.10)|
>
> That being said, I'm not sure where exactly this is going and how much
> it will change Simgear and Flightgear, so it may cause the CMake files
> to become complex. I'll also look into this, since I might be missing
> something.
>
> On another note, reading up on EXPORT, there is supposedly an IMPORT
> in another library/project that uses the file from EXPORT to get the
> version. If this is true, then there may be some problems in Debian
> and Ubuntu, since each source is compiled individually, along with the
> development packages of necessary libraries. That being said, if it is
> just a file containing the version info, I suppose the file could be
> included in the development packages for simgear, which will then be
> available when flightgear is built.
>
> On Thu 17 Oct 2013 06:31:12 PM EDT, James Turner wrote:
>>
>>
>> On 17 Oct 2013, at 22:45, Saikrishna Arcot <saiarcot895@gmail.com
>> <mailto:saiarcot895@gmail.com>> wrote:
>>
>>>
>>> I noticed the Simgear CMake has moved towards using EXPORT, and that one
>>> of the two libraries depends on the other. However, dependency in EXPORT
>>> is only supported in CMake 2.8.10, but Ubuntu Precise and Quantal ship
>>> with CMake 2.8.7 and 2.8.9, and therefore compilation of Simgear fails
>>> on those two distros (Ubuntu Raring and Saucy work fine, since they have
>>> at least CMake 2.10). Any chance an if-conditional can be added to allow
>>> for the use of CMake <2.8.10?
>>
>>
>> Ah, that's what is happening!
>>
>> 'moving towards' is correct, I am experimenting but didn't yet start
>> using the exported Config files, and I need to add more state to them.
>> I wanted to see what each platform generates, but I didn't expect the
>> mere act of requesting the exports to cause these issues.
>>
>> I think I can fix this by combining both exports into a single export
>> group - but I'm still trying to find adequate docs on this area. If
>> that's not possible, what would the conditional you're proposing look
>> like?
>>
>> Kind regards,
>> James
>>
>>
>>
>> ------------------------------------------------------------------------------
>> October Webinars: Code for Performance
>> Free Intel webinars can help you accelerate application performance.
>> Explore tips for MPI, OpenMP, advanced profiling, and more. Get the
>> most from
>> the latest Intel processors and coprocessors. See abstracts and
>> register >
>> http://pubads.g.doubleclick.net/gampad/clk?id=60135031&iu=/4140/ostg.clktrk
>>
>>
>> _______________________________________________
>> Flightgear-devel mailing list
>> Flightgear-devel@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/flightgear-devel
>> --
>> Saikrishna Arcot

------------------------------------------------------------------------------
October Webinars: Code for Performance
Free Intel webinars can help you accelerate application performance.
Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from 
the latest Intel processors and coprocessors. See abstracts and register >
http://pubads.g.doubleclick.net/gampad/clk?id=60135031&iu=/4140/ostg.clktrk
_______________________________________________
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel
[prev in list] [next in list] [prev in thread] [next in thread]