Talk:TerraGear scenery build server: Difference between revisions

Jump to navigation Jump to search
m (http://forum.flightgear.org/viewtopic.php?f=5&t=14163&start=15#p200802)
Line 11: Line 11:


== Packaging (saiarcot895 ) ==
== Packaging (saiarcot895 ) ==
I think I can help here.
'''Hooray:'''Obviously, one major part of this would involve installing/packaging SimGear and TerraGear as *.deb files.
This would greatly simplify the installation - we do have several instructions related to this, and even a script - so we could change the script to build SG/TG and then package things afterwards.


Part of the work may have been already done. We are distributing simgear in two packages (since there are two libraries): libsimgearcore and libsimgearscene. libsimgearcore doesn't have any graphical dependencies; it only depends on libc6. libexpat, libgcc1, libstdc++6, and zlib1g. The only drawback here is that the -dev package includes headers for both libraries, which would require both libraries be installed. Would libsimgearcore be equivalent to the library produced by SIMGEAR_HEADLESS?
Ideally, SimGear would be built in "headless" mode - i.e. minus all the OSG dependencies, no sound etc required: http://wiki.flightgear.org/Building_using_CMake#SimGear_Build_Options
 
So we would first of all end up with something like "libsimgear-headless-dev" which could be used to build TerraGear.
The next step would be creating a package for TerraGear itself that depends on SimGear-headless-dev
 
Once these two steps are completed, setting up TerraGear on Linux should become much more straightforward.
And we could use these packages to set up a TerraGear build server.
 
All this will be based on TurnKeyLinux, which is a debian/wheezy based distro, intended for "remastering" - so that new virtual appliances can be easily created, and exported - so that others can install an ISO file to get a working TG setup.
 
For now, I simply built SG headless (libsimgearcore) and installed it system-wide and it's working properly.
 
But obviously it would be better to come up with packages for both, SG and TG (64bit).
Which would be useful for all debian/ubuntu users, not just this particular effort.
 
Also, we would need to publish those packages, so that people only need to add the repo to download updates automatically.
 
Overall, this would help greatly simplify TG deployment obviously, no matter if it's about having a build server or not.
 
Looking at SG/FG, the best option seems to be to use cmake's cpack support to create packages: http://www.cmake.org/Wiki/CMake:CPackPackageGenerators
 
:'''saiarcot895''': I think I can help here.
 
:Part of the work may have been already done. We are distributing simgear in two packages (since there are two libraries): libsimgearcore and libsimgearscene. libsimgearcore doesn't have any graphical dependencies; it only depends on libc6. libexpat, libgcc1, libstdc++6, and zlib1g. The only drawback here is that the -dev package includes headers for both libraries, which would require both libraries be installed. Would libsimgearcore be equivalent to the library produced by SIMGEAR_HEADLESS?


== TerraGear & TerraGear GUI (reeed) ==
== TerraGear & TerraGear GUI (reeed) ==

Navigation menu