Talk:Building FlightGear - Debian: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
(issues with compiling 3.6.0) |
||
Line 10: | Line 10: | ||
: [[User:Flughund|Flughund]] ([[User talk:Flughund|talk]]) 01:21, 3 September 2015 (EDT) | : [[User:Flughund|Flughund]] ([[User talk:Flughund|talk]]) 01:21, 3 September 2015 (EDT) | ||
== Issues while compiling FG 3.6.0 == | |||
After writing "git checkout origin/release/3.6.0" | After writing "git checkout origin/release/3.6.0" | ||
I get this message: | I get this message: | ||
Note: checking out 'origin/release/3.6.0'. | 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 | |||
{{unsigned|17:19, 5 September 2015|Vinya}} | |||
: 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. <code>cd simgear.git</code> instead of <code>mkdir $FG_SRC_DIR/build-sg; cd $FG_SRC_DIR/build-sg</code>. I am lurking on [[IRC]] as debdog, if you have further questions/issues. | |||
: [[User:Flughund|Flughund]] ([[User talk:Flughund|talk]]) 12:33, 5 September 2015 (EDT) | |||
Revision as of 16:34, 5 September 2015
Git problems
git seems no longer to be working
—This unsigned comment was added by Vinya (Talk | contribs) 16:28, 1 September 2015 (UTC)
- 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)
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 ofmkdir $FG_SRC_DIR/build-sg; cd $FG_SRC_DIR/build-sg
. I am lurking on IRC as debdog, if you have further questions/issues.
- You seemed to have messed up the steps somehow.
- Flughund (talk) 12:33, 5 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: http://sourceforge.net/mailarchive/message.php?msg_id=29695942
- 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)