Thread: cygwin setup questions

*looks*

Note: Each time you select one, you may additionally get others selected automatically. Leave those checked, too.

The ones you want are "gcc-core" and "gcc-g++". Subversion, you just want "subversion".

You also will want "X11/libfltk-devel" and "X11/libfltk1.1-gdi" for the GUI

Oh! Hrm. I'm looking and I don't see gpsd in there. GPS isn't a requirement for my software, although obviously the google earth stuff won't work without it. That might be a separate compilation job, I'll look later.

Gary (-;

*looks*

Note: Each time you select one, you may additionally get others selected automatically. Leave those checked, too.

The ones you want are "gcc-core" and "gcc-g++". Subversion, you just want "subversion".

You also will want "X11/libfltk-devel" and "X11/libfltk1.1-gdi" for the GUI

Oh! Hrm. I'm looking and I don't see gpsd in there. GPS isn't a requirement for my software, although obviously the google earth stuff won't work without it. That might be a separate compilation job, I'll look later.

Gary (-;

Well I have a funny problem. I downloaded required packages and installed from the local directories. When I run
cmake .. #
it tried to invoke gmake.exe from a Matlab (Windows version) subdirectory and failed. I searched the disk and that's the only place that has gmake. I thought I would look into the install log but I only found the log of the downloading, not the installing. Any suggestions?

Perhaps you need cygwin's "devel/make" aswell?

Alternatively, "gmake" is gnu make usually, which is what you have. You could just symlink them:
ln -s /usr/bin/make /usr/bin/gmake

I think cmake might have an option to choose which "make" to use with the "Unix Makefiles" target but I can't remember what it is.

Gary (-;

Sorry for my continuing stupid questions.

I made a tiny little step forward:
I found some parameters in the file "CMakeCache.txt" points to the Windows Matlab gmake.exe so I changed them to /usr/bin/make and that worked.

But then there are some more things that were not found:

$ cmake .. #
...
-- Couldn't find libgps
-- Couldn't find dbus
-- Looking for ptsname_r
-- Looking for ptsname_r - not found
...
cygwin warning:
MS-DOS style path detected: C:/msys/1.0/local/include/fftw3.h
Preferred POSIX equivalent is: /cygdrive/c/msys/1.0/local/include/fftw3.h
CYGWIN environment variable option "nodosfilewarning" turns off this warning.
Consult the user's guide for more details about POSIX paths:
http://cygwin.com/cygwin-ug-net/usin...sing-pathnames
-- Couldn't find fftw3: required for building obdfft
...
-- Looking for getaddrinfo
-- Looking for getaddrinfo - not found.
-- Looking for getaddrinfo
-- Looking for getaddrinfo - found
...
-- Looking for BTPROTO_RFCOMM
-- Looking for BTPROTO_RFCOMM - not found.
-- Couldn't find libftdi, required for building obdftdipty
-- Configuring done
-- Generating done
-- Build files have been written to: /obdgpslogger-0.15/build

and some of them generated new entries in the file again pointing to some items in the Windows Matlab directories:

...
//Path to a file.
FFTW3_INCLUDE_DIR:PATH=FFTW3_INCLUDE_DIR-NOTFOUND

//Path to a library.
FFTW3_LIBRARY:FILEPATH=/cygdrive/c/Program Files/MATLAB/R2008b/bin/win32/./libfftw3.dll

...

I suppose the "libgps" is the missing gpsd you mentioned. How about others?

Not stupid at all!

libgps is missing gpsd, yeah. It's not necessary, at least to start.

dbus you don't want, and is disabled by default in svn.

fftw is used in only one of the tools I build, a little thing to do fourier transforms on data. This one's in the category of "if you have to ask, you don't want it".

btproto_rfcomm is used for the obd simulator to simulate a bluetooth device. You may find it useful to see the obdsim doing something just so you don't have to walk out to your car, but you don't want the bluetooth bit.

libftdi is used to build a tool so that linux machines with braindamaged or nonexisted ftdi drivers can communicate with ftdi devices.

Overall... you don't need anything that you're missing. At its heart, obdgpslogger has almost zero actual, real, dependencies for core functionality.

Just type "make" :-)

I also recommend checking out the svn version. 0.15 is a bit old at this point, I really oughta do a new release. To do an svn checkout:
svn co svn://svn.icculus.org/obdgpslogger/trunk obdgpslogger-trunk

Gary (-;

Originally Posted by chunkyks

Not stupid at all!

libgps is missing gpsd, yeah. It's not necessary, at least to start.

dbus you don't want, and is disabled by default in svn.

fftw is used in only one of the tools I build, a little thing to do fourier transforms on data. This one's in the category of "if you have to ask, you don't want it".

btproto_rfcomm is used for the obd simulator to simulate a bluetooth device. You may find it useful to see the obdsim doing something just so you don't have to walk out to your car, but you don't want the bluetooth bit.

libftdi is used to build a tool so that linux machines with braindamaged or nonexisted ftdi drivers can communicate with ftdi devices.

Overall... you don't need anything that you're missing. At its heart, obdgpslogger has almost zero actual, real, dependencies for core functionality.

Just type "make" :-)

Thanks for the explanations. Very helpful. "make" worked. I tried to run obdgui.exe and got this:

$ ../bin/obdgui
Can't open display:

I also recommend checking out the svn version. 0.15 is a bit old at this point, I really oughta do a new release. To do an svn checkout:
svn co svn://svn.icculus.org/obdgpslogger/trunk obdgpslogger-trunk

Gary (-;

Which directory should I run svn from?

That line is going to check out into a new directory called "obdgpslogger-trunk". So I usually create a directory called "src" in my home dir in cygwin and then run the command from within that, but whatever works for you

Gary (-;

Thanks! How about the "Can't open display" problem?