On 04/11/11 00:08, Adrian Musceac wrote:
> On Friday, November 04, 2011 01:05:25 Jon Stockill wrote:
>>
>> Have we changed the default data directory again? cmake outputs this:
>> -- Using default data-dir: /usr/lib/FlightGear
>> There doesn't appear to be any way to set it within ccmake or from t
On 04/11/11 00:00, Martin Spott wrote:
> Jon Stockill wrote:
>
>> Simgear doesn't seem to install to the correct directory on 64 bit
>> systems any more - there doesn't seem to be any way to tell it to use
>> /usr/lib64 instead of /usr/lib
>
> That's in "LIB_POSTFIX". Try:
>
># ~> cmake -D CMA
On Friday, November 04, 2011 01:05:25 Jon Stockill wrote:
>
> Have we changed the default data directory again? cmake outputs this:
> -- Using default data-dir: /usr/lib/FlightGear
> There doesn't appear to be any way to set it within ccmake or from te
> commandline.
>
I believe it's FG_DATA_DI
Jon Stockill wrote:
> Simgear doesn't seem to install to the correct directory on 64 bit
> systems any more - there doesn't seem to be any way to tell it to use
> /usr/lib64 instead of /usr/lib
That's in "LIB_POSTFIX". Try:
# ~> cmake -D CMAKE_INSTALL_PREFIX=/usr -D LIB_POSTFIX=64 [...]
Che
I've converted my build script over to cmake (I'll be updating my
jenkins server once a few niggles have been ironed out) - these are:
Simgear:
Simgear doesn't seem to install to the correct directory on 64 bit
systems any more - there doesn't seem to be any way to tell it to use
/usr/lib64 in
-Original Message-
From: Geoff McLane
Sent: Thursday, November 03, 2011 2:05 AM
To: FlightGear developers discussions
Subject: Re: [Flightgear-devel] moving map of Hondajet or Da-42 //
nextscenerygeneration
Geoff
The slow upload is because this is URL is my own PC, via Apache.
I hav
2011/11/3 Vadym Kukhtin
>
> One thing I noticed, in FG' log there is line
> -- Found SimGear: /usr/local/lib/libSimGear.so
>
> But, it cant anyway found SG in /opt dir, coz:
> v@leo:/opt/sg-git/lib$ ls
> libsgbucket.a libsgephem.a libsgmath.a libsgprops.a libsgsky.a
> libsgthreads.a
On 3 Nov 2011, at 16:37, Vadym Kukhtin wrote:
> Couple weeks ago I tried build FG with ccmake, but fail. I wrote about it to
> ML, but no response. And I continuue build with ./configure.
I apologise, I thought I had responded to your original email.
> So, SG compiles with ccmake like a charm,
On 3 Nov 2011, at 13:19, Christian Schmitt wrote:
>> That's stock Debian 6 alias Squeeze, the current stable, GCC-4.4.5 and
>> Glibc-2.11.2, if it matters,
>
> Ok, I observed the following: compiling the raw2ascii as "Release" leads to
> the error (on Debian). When compiling as "Debug" it works
Hi. I compile SG-FG for few years.
Couple weeks ago I tried build FG with ccmake, but fail. I wrote about it
to ML, but no response. And I continuue build with ./configure.
But from now, it impossible...
So, SG compiles with ccmake like a charm, but FG show error:
http://pastebin.com/gmEicCXB
Both
On Thu, Nov 3, 2011 at 8:19 AM, Christian Schmitt wrote:
> Martin Spott wrote:
>
> > That's stock Debian 6 alias Squeeze, the current stable, GCC-4.4.5 and
> > Glibc-2.11.2, if it matters,
>
> Ok, I observed the following: compiling the raw2ascii as "Release" leads to
> the error (on Debian). When
Hi,
> By the way, I noticed that cmake checks for FLTK installed.
> Where is that used?
FLTK is used by fgadmin
Regards,
-Fred
--
RSA(R) Conference 2012
Save $700 by Nov 18
Register now
http://p.sf.net/sfu/rsa-sfdev2dev
Martin Spott wrote:
> That's stock Debian 6 alias Squeeze, the current stable, GCC-4.4.5 and
> Glibc-2.11.2, if it matters,
Ok, I observed the following: compiling the raw2ascii as "Release" leads to
the error (on Debian). When compiling as "Debug" it works here.
Chris
Martin Spott wrote:
> Christian Schmitt wrote:
>
>> Martin: Can you tell me under which OS this is happening? So I can try to
>> reproduce it in a VM.
>
> That's stock Debian 6 alias Squeeze, the current stable, GCC-4.4.5 and
> Glibc-2.11.2, if it matters,
>
I guess it matters, because I get e
On Thu, 2011-11-03 at 07:30 -0500, Curtis Olson wrote:
> Hi Alasdair,
>
>
> There very first thing I do when I see any X11 or OpenGL related
> errors that are new to my system is re-install the nvidia drivers. I
> usually install updates whenever they come out so there's a good
> chance (for me)
Hi Alasdair,
There very first thing I do when I see any X11 or OpenGL related errors
that are new to my system is re-install the nvidia drivers. I usually
install updates whenever they come out so there's a good chance (for me)
that one of those updates will overwrite something in the X11 or Open
Just pulled the latest git (with cmake). The build went just fine, but
the executable fails for me with:
"Got an X11ErrorHandling call display=0x18eea80 event=0x7fff7be946a0
BadWindow (invalid Window parameter)
Major opcode: 137
Minor opcode: 4
Error code: 3
Request serial: 57
Current serial: 57
Christian Schmitt wrote:
> Martin: Can you tell me under which OS this is happening? So I can try to
> reproduce it in a VM.
That's stock Debian 6 alias Squeeze, the current stable, GCC-4.4.5 and
Glibc-2.11.2, if it matters,
Martin.
--
Unix _IS_ user friendly - it's just selective abo
James Turner wrote:
> With some local changes to Simgear/next, but I am 'fairly sure' they don't
> relate to path/file/string handling. (Some changes in the SGOceanTile
> handling)
>
I just tested this as well (without your fix) and it works here too. Even
when using Martin's pathnames.
gl
James Turner wrote:
> On 2 Nov 2011, at 19:48, Martin Spott wrote:
>>> Fixed now, at least, it generated a ton of .dem files for me.
>>
>> Really ? And you're on simgear/next and terragear-cs/cmake-integration
>> without local changes ?
>
> With some local changes to Simgear/next, but I am 'fai
On 2 Nov 2011, at 19:48, Martin Spott wrote:
>> Fixed now, at least, it generated a ton of .dem files for me.
>
> Really ? And you're on simgear/next and terragear-cs/cmake-integration
> without local changes ?
With some local changes to Simgear/next, but I am 'fairly sure' they don't
relate
As far as my (still limited) understanding goes, gitorious needs to know the
public SSH key of the machine you're uploading from. Just login at gitorious,
go to dashboard, and click Manage SSH keys.
HTH,
Durk
On 03 Nov 2011, at 09:03, Michael Sgier wrote:
> Ok I did a fgdata clone:
>
> https
Michael Sgier wrote:
> Ok I did a fgdata clone:https://gitorious.org/~scrat/fg/scrats-fgdata
Why did you go through all the hassle of creating an isolated workspace
instead of cloning the repo directly at Gitorious ?
Martin.
--
Unix _IS_ user friendly - it's just selective about who it
Ok I did a fgdata clone:https://gitorious.org/~scrat/fg/scrats-fgdata
and pulled that ~3.5GB. Now I've added the aircrafts but push gives:
michael@ubuntu:/media/DATA/FGFS/install/fgfs/fgdata$ git push origin master
fatal: protocol error: expected sha/ref, got '
---
Hi all
I see so many good and nice additions for FlightGear, why not follow
former "polls" I’ve seen here and organize a small award in december,
somthing like "best add-on development" for FlightGear ?
Possibility to give two awards, one from a public i.e. as a vote in the
forum and another a
25 matches
Mail list logo
