Talk:Building FlightGear - Debian

From FlightGear wiki
Revision as of 18:57, 24 September 2015 by Flughund (talk | contribs)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigation Jump to search

Git problems

git seems no longer to be working

This unsigned comment was added by Vinya (Talk | contribs) 16:28, 1 September 2015 (UTC)

Could you provide more info, please!
Flughund (talk) 09:00, 2 September 2015 (EDT)
Just went through the steps to compile the git version and it went fine. Without further info I am not able to investigate.
Flughund (talk) 01:21, 3 September 2015 (EDT)

Thank you very much. Problems have been solved. Git probably had no good connection that day. Later it worked. The building also worked.

This unsigned comment was added by Vinya (Talk | contribs) 11:03, 7 September 2015 (UTC)

Issues while compiling FG 3.6.0

After writing "git checkout origin/release/3.6.0" I get this message:

Note: checking out 'origin/release/3.6.0'.

You are in 'detached HEAD' state. You can look around, make experimental
changes and commit them, and you can discard any commits you make in this
state without impacting any branches by performing another checkout.

If you want to create a new branch to retain commits you create, you may
do so (now or later) by using -b with the checkout command again. Example:

 git checkout -b new_branch_name

HEAD is now at fdcef8e... Fix #1783: repeated error message on console
agonzalez@debian-ul30a:~/Flightgear/src/simgear.git$ cd simgear.git
bash: cd: simgear.git: file o directory does not exist

This unsigned comment was added by Vinya (Talk | contribs) 17:19, 5 September 2015 (UTC)

About the first code block:
This is just a warning and for plain users it's ok to compile from that state. And since origin/release/3.6.0 is not a branch for development, this even is ok for developers. There's only one reason for why one would want to create a local branch from it: to apply patches. I am open for discussion on that point, though. I am not entirely certain whether this is 'the correct' way, especially because it might confuse users without any git experience at all. On the other hand creating that branch is useless for the vast majority and might mislead users who intend to learn more about using git.
About the second code block:
You seemed to have messed up the steps somehow. cd simgear.git instead of mkdir $FG_SRC_DIR/build-sg; cd $FG_SRC_DIR/build-sg. I am lurking on IRC as debdog, if you have further questions/issues.
Flughund (talk) 08:09, 7 September 2015 (EDT)


fgdata for 3.6.0 are not in the repositories...

This unsigned comment was added by Vinya (Talk | contribs) 11:03, 7 September 2015 (UTC)

Yes, this has not yet been bundled, hence the WIP tag at the top of the page. We have to wait untill 3.6.0 is released. If you have the fgdata git repo you can check out the release branch:
cd $FG_INSTALL_DIR/fgdata
git checkout -b 3.6.0 origin/release/3.6.0
Thank you very much for reporting, it's nice to have some user feedback!
Flughund (talk) 08:09, 7 September 2015 (EDT)

FYI: fgdata for the release candidate is available now Flughund (talk) 14:57, 24 September 2015 (EDT)

PLIB notes

  • I had to use the old revision to compile, in two different computers (both with Squeeze).
The problem has been reported to plib devel mailing list:
  • FlightGear 2.6.0 compiles with the Squeeze own plib, but 2.8.0 does not.
Hmh, that's interesting....

Flughund 04:46, 20 August 2012 (EDT)