Hi Gerrit, hi Joerg, the configure creates now working makefiles...
I found out, that the spaces in the compiler path don't matter, that's good. and mount C: gives a warning, but is shown as mounted, that's also good, even though it seems not to be necessary... I re-installed "Microsoft Visual C++ Toolkit 2003" and "Microsoft Visual Studio .NET" to the default locations and it compiles now. I searched in circles, because the standard includes are not found (from the "Core SDK"), and I try now to include the headers using --with-add-incdir, but then I'm back at the "Unquoted String" problem. Where do I set these paths? is there an environment variable similar to CXXFLAGS? Sorry, my knowledge about these mechanisms under windows is very little... Thanks for all your help. best regards, daniel On Mon, 3 Jan 2005 11:25:17 +0100, Jörg Bornemann <[EMAIL PROTECTED]> wrote: > 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 > > -- Daniel -mcJack- Walz Dipl.-Ing. of computer-visualistics email: [EMAIL PROTECTED] icq#: 70137980 pgp: DAF0B6EF at: wwwkeys.de.pgp.net http://www.cs.uni-magdeburg.de/~dwalz/ ------------------------------------------------------- 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
