Ok, I see now that in simgear-2.10.tar.bz2 the top level file "version"
does report 2.10.0 but the simgear/version.h file is saying 2.8.0
So my question are:
1. for an out-of-source build, why is the build system writing files in the
source tree? Can we fix that?
2. what is the proper cmake fix here so it doesn't happen in the future?
Thanks,
Curt.
On Mon, Feb 18, 2013 at 8:26 AM, Curtis Olson <curtol...@flightgear.org>wrote:
> Hi Christian,
>
> I completely blew away my "build_flightgear" and "build_simgear"
> directories so they should be totally clean for the latest version of the
> source code. Are our cmake rules doing something they shouldn't and
> writing files in the original source tree when you do out of source builds?
>
> I thought (I was 100% sure until now that you say there was a problem)
> that I looked at version.h in my "build_simgear" directory and it said
> 2.10.0
>
> I really want to get this fixed as quickly as possible, but I'm confused
> as to where things could be going wrong or how to fix it. Back in the day I
> had the automake tools really figured out for myself at a deep level, but I
> unfortunately don't have that same level of groking for the cmake tools.
>
> Curt.
>
>
> On Mon, Feb 18, 2013 at 4:31 AM, Christian Schmitt <ch...@ilovelinux.de>wrote:
>
>> Curt,
>>
>> I noticed the SG/FG packages got updated on the mirrors. So I checked
>> them out again: still the same issue. How did you create the source
>> tarballs? Having the version number 2.8 in it looks like they were
>> created from an older, used git clone and not a fresh or cleaned up
>> one. The tarballs should only contain files that are in git, nothing
>> that gets created during configure/compile time.
>>
>> Chris
>>
>>
>>
>> Curtis Olson wrote:
>>
>> > Certainly this is my fault, however, I must misunderstand something
>> about
>> > cmake for this to happen. Can someone enlighten me and tell me what
>> I
>> > need
>> > to do to fix this? Maybe there is something we can tweak in the
>> future if
>> > the default behavior requires manual intervention to achieve the
>> correct
>> > outcome?
>> >
>> > Thanks for checking this out Chris.
>> >
>> > Curt.
>>
>>
>> ------------------------------------------------------------------------------
>> The Go Parallel Website, sponsored by Intel - in partnership with Geeknet,
>> is your hub for all things parallel software development, from weekly
>> thought
>> leadership blogs to news, videos, case studies, tutorials, tech docs,
>> whitepapers, evaluation guides, and opinion stories. Check out the most
>> recent posts - join the conversation now.
>> http://goparallel.sourceforge.net/
>> _______________________________________________
>> Flightgear-devel mailing list
>> Flightgear-devel@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/flightgear-devel
>>
>
>
>
> --
> Curtis Olson:
> http://www.atiak.com - http://aem.umn.edu/~uav/
> http://www.flightgear.org - http://gallinazo.flightgear.org
>
--
Curtis Olson:
http://www.atiak.com - http://aem.umn.edu/~uav/
http://www.flightgear.org - http://gallinazo.flightgear.org
------------------------------------------------------------------------------
The Go Parallel Website, sponsored by Intel - in partnership with Geeknet,
is your hub for all things parallel software development, from weekly thought
leadership blogs to news, videos, case studies, tutorials, tech docs,
whitepapers, evaluation guides, and opinion stories. Check out the most
recent posts - join the conversation now. http://goparallel.sourceforge.net/
_______________________________________________
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel
