Hi Daniel!
sounds reasonable to me, so I try to avoid this.
The only problem is, that any of the default paths for the
compiler has several spaces:
[...]
You can hardly install VS .NET into a directory without spaces.
But that's not the problem. The configure script doesn't find your compiler
because it is not located in one of the above directories.
As far as I can see there is no option --with-compiler-dir or similar
(or did I miss it?) and giving configure the whole path to the cl.net2003
makes it loosing its config:
AFAIK there's no such option.
The compiler directories are hard-coded in the configure-script.
You may try to hack it: search for code lines that look like this
for drive in c d e f g; do
for progdir in "Program Files" "Programme"; do
for vsnet in "Microsoft Visual Studio.NET 2003" "Microsoft Visual
Studio .NET 2003"; do
if test -d "/cygdrive/$drive/$progdir/$vsnet/"; then
ac_gdz_find_prog_dir_result="/cygdrive/$drive/$progdir/$vsnet"
break 3
fi
done
done
done
and replace "Microsoft Visual Studio .NET 2003" with the path of your
Platform SDK compiler f.e. "Microsoft Platform SDK/bin".
There are at least two places where you have to replace the path.
Hope it helps,
Joerg.
-------------------------------------------------------
The SF.Net email is sponsored by: Beat the post-holiday blues
Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek.
It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt
_______________________________________________
Opensg-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/opensg-users
