[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
RE: [cdt-core-dev] Custom Toolchain w/MBS on Windows - backslashes vsforward slashes in paths
|
Personally I use gmake (GNU make) compiled directly for Windows, which
itself can handle either Windows or UNIX-style paths. I'm lucky though
because the TI compiler can handle UNIX-style paths itself. I guess
you're not so lucky with your compiler :-(
___________________________________________
Chris Recoskie
Software Designer
Texas Instruments, Toronto
http://eclipse.org/cdt
> -----Original Message-----
> From: cdt-core-dev-bounces@xxxxxxxxxxx [mailto:cdt-core-dev-
> bounces@xxxxxxxxxxx] On Behalf Of John K
> Sent: Tuesday, October 18, 2005 2:29 PM
> To: cdt-core-dev@xxxxxxxxxxx
> Subject: [cdt-core-dev] Custom Toolchain w/MBS on Windows -
backslashes
> vsforward slashes in paths
>
> Hi all,
>
> I'm having a heck of a time integrating our toolchain
> (custom for a 16-bit x86 embedded proc) with the
> Managed Build System. I've been able to create a
> plug-in, create a project, and get the builder to
> generate a makefile and invoke "make", but make uses
> forward slashes in all of the source file path names
> when it calls the compiler command. How do I get it
> to use backslashes?
>
> I've searched the MBS, eclipse docs, and the web for
> literally two days and I haven't found anything that
> addresses it. I found an example of how to integrate
> MSVC with Eclipse (using make), but they used a really
> really simple example that didn't need any relative
> paths to get to the source code modules!
>
> When I try building, I get:
>
> **********
> Building file: ../Src/ODemo.c
> Invoking: Custom C/C++ Compiler
> xcc Src/ODemo.obj ../Src/ODemo.c
> XXXXX Compiler Version X
> Copyright (c) XXXXX, Inc. All Rights Reserved.
>
> Error: Invalid optimization option '.obj'
> Error: Command line contains more than one file to
> compile
> Error: Invalid option '/Src'
> Error: Invalid optimization option '.c'
> Unable to open '..'
> make: *** [Src/ODemo.obj] Error 9
> **********
>
> I'm guessing it's assuming that I want it to run
> inside the Cygwin environment, but I've read in the
> GNU make docs that it can be run in a DOS style shell
> by changing the SHELL variable. I tried making a
> makefile.init with SHELL=command.com and I get:
>
> **********
> E:\Work\ODemo>Specified COMMAND search directory bad
> Parameter format not correct
> Too many parameters
> Invalid switch
> Too many parameters
> Invalid switch
> Invalid switch
> Microsoft Windows 2000 [Version 5.00.2195]
> (C) Copyright 1985-2000 Microsoft Corp.
> **********
>
> If I try SHELL=cmd.exe I get:
>
> **********
> E:\Work\ODemo\Release>Microsoft Windows 2000 [Version
> 5.00.2195]
> (C) Copyright 1985-2000 Microsoft Corp.
>
> '++' is not recognized as an internal or external
> command,
> operable program or batch file.
> make: *** [Src/ODemo.obj] Error 1
> **********
>
> I'm guessing the '++' error is because make is giving
> its echo statements to cmd.exe: 'Invoking: Custom
> C/C++ Compiler'.
>
> Any ideas?
>
> Also, are there any better make/build utilities out
> there for Eclipse CDT projects on Windows?
>
> Thanks,
>
> John
>
>
>
>
>
>
>
>
> __________________________________
> Yahoo! Mail - PC Magazine Editors' Choice 2005
> http://mail.yahoo.com
> _______________________________________________
> cdt-core-dev mailing list
> cdt-core-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/cdt-core-dev
