From: Tatsuro M. <tma...@ya...> - 2008-11-23 04:15:36
|
Hello The mail from Petr does not have any relation to the gnuplot on cygwin. You need not to change anthing for your building the cygwin gnuplot from thr cvs trees. However the cygwin is the unixy, so that it is good to convinient to use the unixy way to produce cygwin binary. Please read 'Downloading sources from the CVS repository' and Building from CVS http://gnuplot.info/development/index.html You need not use to config.cyg if you will use the traditinal Unixy way like following. ./prepare # which was reuired for to build the configure script from cvs sources ./configure make make check make install-strip ******************** BTW I am mingw user and the cvs version of gnuplot for windows (not for cygwin) can be built from mingw environments. It is required to collect external addtional libraries from GnuWin32 and GTK (Gimp Tool Kit.) and Microsoft help workshop. It is of course that you can build gnuplot for windows by MSVC complier like VC2005 or VC2006 Express Edition. ********************* Regards Tatsuro --- don taber <dt...@to...> wrote: > > 2. Console-mode executable gnuplot.exe was added to the package. This is > > now the recommended binary to be used under Windows -- the same name > > Sorry if this is a stupid question, but I haven't been paying much > attention to this thread. Is 'gnuplot.exe' simply what you get when > you use the *nix configure/Makefile in a cygwin environment? > And what makefile generates the 'wgnuplot_pipes.exe' ? I always > use makefile.cyg for generating windows binaries and I've never > seen this mysterious thing appear :-) > > Maybe a general cleanup of the various {makefile,config}.??? in config/ > is called for. Or at least a README that explains what they all > do. This is by no means clear from their names. For example, > makefile.nt is for VisualC 6.x but who would guess this from > the name? > -------------------------------------- Power up the Internet with Yahoo! Toolbar. http://pr.mail.yahoo.co.jp/toolbar/ |