Hi Alan,
> This build-tree change is a nice first step toward getting ctest working on
> windows. Of course, the problem still remains that the current ctest uses
> the shell scripts plplot-test.sh and test*.sh, and I assume (but correct me
> if I am wrong) those scripts will not work on bare windows.
No, I just was able to make them work. There are some bash-ports
available (apart from cygwin, msys), but the problem here is (also see
below), that you always run into problems sooner or later regarding
filenames and so on. I was always looking for a bash I can use in
Windows, but after a long series of failings, I came to the conclusion,
that it is better to always use the native tools of the OS you are
working on. Anyway, one exception are the GNUWin32 Tools you can find
here: gnuwin32.sf.net . They provide ports of various gnu tools, and
they did a good job, they just work also in the Windows CLI without
problems, and regardless if you use \ or / or whatever. I think for the
test scripts you need at least the core utils and sed (on the gnuwin32
homepage click left packages). Just download the binary package and the
dependency package as zips and unzip them somewhere (e.g. C:\GNUWin32)
and add the path to the environment variable (set
PATH=C:\GNUWin32\bin;%PATH%). But GNUWin32 doesn't provide a bash, so we
need to use win-bash: winbash.sf.net . At least it is a recent port, but
accepts for example only linux style pathnames. Anyway, download
win-bash.exe and copy it into GNUWin32\bin as bash.exe and sh.exe. So
this should do the trick, if another gnu tool is needed get it from
gnuwin32.
If I run now ctest in my plplot build directory it runs the c and c++
test successfully. But the java test fails, because .... of the same
problems I always failed so far. Bash handles everything like in Linux
and the Gnuwin32 tools except that, but Java expects Windows like syntax
....
In test_java.sh the important command line is:
java -classpath ${javadir}:${PLPLOT_CLASSPATH} .....
The colon between javadir and PLPLOT_CLASSPATH is good for Linux, but
for Windows obviously not (e.g. C:\ :), but if I replace the colon with
a semicolon, which would be windows style, bash chokes up, since this
ends a command or similar (I'm not a bash guru). So, again another
failure to use bash in a Windows environemnt. Sigh. Anyway, I think we
might be able to fix this, but I don't want to change this on my own.
Alan, could you think of a solution here, which would work for Linux and
Windows? Actually I would only need PLPLOT_CLASSPATH since it contains
the full path to plplot.jar.
> I am completely
> unfamiliar with the windows scripting constraints, but if there is no easy
> way to modify those scripts so they will also work on windows, then perhaps
> we should use the equivalent of those scripts in python or perl for the
> windows case? (I mentioned python first because I understand it and don't
> understand perl, but if the windows developers are more familiar with perl,
> that is the scripting language they should probably use.)
In the long run, I think python scripts would be much better. Perl is
not too much used in Windows I think. Python is very easy to install and
is cross platform, so this would be my first option here (though I never
did anything in python). But since I came that far with the bash scripts
and it is kind of easy, and the normal plplot user shouldn't need it
anyway, we should stick with the bash scripts, since this minimizes our
efforts. We just need a little tweaking here and there.
>
> This build-tree enhancement for windows developers is great, and I look
> forward to ctest eventually working for windows as a result, but it leads to
> the question of whether the equivalent of "make install" is supported on
> windows.
Yes, "make install" works, for all "make"s I tested so far (nmake,
wmake, mingw32-make, ...)
> I hope it is since "make install" collects all essential data and
> builds in a convenient and compact way for the user. If the equivalent of
> make install is supported, then you should check whether you have to modify
> all the INSTALL commands for the windows case to be consistent with the new
> build-tree location of libraries or whether cmake automatically knows what
> to do when LIBRARY_OUTPUT_PATH is set.
Cmake knows where it put the dll and exe files, regardless where they
are (if you set the LIBRARY_OUTPUT_PATH), no problems here.
So, long story short, ctest works now, with small problems though. I
wasn't actually successful running the plplot-test.sh script in the
examples folder of the install directory (share/plplot-5.7.1), but this
would need also minor tweaking.
Arjen, would you willing to also try to install this to make ctest work?
Werner
--
Dipl. Ing. Werner Smekal
Institut fuer Allgemeine Physik
Technische Universitaet Wien
Wiedner Hauptstr 8-10
A-1040 Wien
Austria
email: [EMAIL PROTECTED]
web: http://www.iap.tuwien.ac.at/~smekal
phone: +43-(0)1-58801-13463 (office)
+43-(0)1-58801-13469 (laboratory)
fax: +43-(0)1-58801-13499
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Plplot-devel mailing list
Plplot-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/plplot-devel
