Jon Berndt wrote:
> Sent: 20 July 2004 06:53
> To: FlightGear developers discussions
> Subject: RE: [Flightgear-devel] Difficulty with building under Cygwin
>
> My SimGear build was not completing. I think it has something to do with
> the move to
> OpenAL. As I was buildi
My SimGear build was not completing. I think it has something to do with the move to
OpenAL. As I was building simgear I got this:
...
checking for library containing alGenBuffers... -lopenal32
checking for library containing alutInit... no
...
Later on, I get this:
g++ -D_REENTRANT -L/usr/loc
> This is a case where you really should go look at the end of the config.log
> file to see *exactly* why the version check is failing.
>
> Curt.
What should one look for in config.log? There appears to be several problems. The
following shows what the worst problem is, however (but I'm not sure h
On Mon, 19 Jul 2004 18:07:43 +0100
"Vivian Meazza" <[EMAIL PROTECTED]> wrote:
I've just downloaded the current cvs version of SimGear and
FlightGear. They both compile under Cygwin straight out of the box.
I would suppose that you have a problem with your path.
Possibly, but I am using the same
Jon Berndt wrote
> Sent: 19 July 2004 15:32
> To: FlightGear developers discussions
> Subject: RE: [Flightgear-devel] Difficulty with building under Cygwin
>
> > > The version looks right, I think (but the $Id date is way off):
> > >
> > > // $Id: ver
Ampere K. Hardraade wrote:
Try including the command: --with-simgear=PATH, whne you are
using ./configure. PATH is the location of SimGear.
Regards,
Ampere
On July 19, 2004 09:49 am, Jon Berndt wrote:
It seems as though, then, that my installation of FlightGear is not looking
for the correct
Try including the command: --with-simgear=PATH, whne you are
using ./configure. PATH is the location of SimGear.
Regards,
Ampere
On July 19, 2004 09:49 am, Jon Berndt wrote:
> It seems as though, then, that my installation of FlightGear is not looking
> for the correct pre-release version of si
Jon Berndt wrote:
> Sent: 19 July 2004 15:32
> To: FlightGear developers discussions
> Subject: RE: [Flightgear-devel] Difficulty with building under Cygwin
>
> > > The version looks right, I think (but the $Id date is way off):
> > >
> > > // $Id: ver
> > > #ifndef _SIMGEAR_VERSION_H
> > > #define _SIMGEAR_VERSION_H
> > >
> > > #define SIMGEAR_VERSION 0.3.6-pre1
> > > ...
> > >
> > > It seems as though, then, that my installation of FlightGear is not looking for
> > > the
> > > correct pre-release version of simgear, but I don't know why. I'v
> > The version looks right, I think (but the $Id date is way off):
> >
> > // $Id: version.h.in,v 1.1.1.1 2002/09/07 02:58:19 curt Exp $
>
> Don't llok at the $Id, it is the Id of version.h.in that is an old template but
> version.h is generated every time you run configure.
Correct. I was jus
Jon Berndt wrote:
> > What is the content of /usr/local/include/simgear/version.h ? ( or wherever you
> > installed SimGear ? )
> >
> > -Fred
>
> The version looks right, I think (but the $Id date is way off):
>
> // $Id: version.h.in,v 1.1.1.1 2002/09/07 02:58:19 curt Exp $
Don't llok at the $
> What is the content of /usr/local/include/simgear/version.h ? ( or wherever you
> installed SimGear ? )
>
> -Fred
The version looks right, I think (but the $Id date is way off):
// $Id: version.h.in,v 1.1.1.1 2002/09/07 02:58:19 curt Exp $
#ifndef _SIMGEAR_VERSION_H
#define _SIMGEAR_VERS
Jon Berndt wrote:
> I updated plib/simgear/flightgear/base from CVS. Built plib and simgear. Checked the
> dates
> on the libs - they're all current. The sources were updated from CVS. I tried
> building
> FlightGear and got this:
>
> ...
> checking for simgear/version.h... yes
> checking for s
13 matches
Mail list logo
