Skip to main content



      Home
Home » Language IDEs » C / C++ IDE (CDT) » adding a blank between -o and the outputname
adding a blank between -o and the outputname [message #153508] Fri, 09 September 2005 08:14 Go to next message
Eclipse UserFriend
Originally posted by: Wagner.rz.rwth-aachen.de

Hi @ all

i have a problem under 2 sparc solaris machines.

Im working with Eclipse 3.1, CDT 3.0 on sparc solaris 9/10, using the
managed make mechanism.

The assembler as (even with SUNStudio 10 Update 1) needs an blank
between the -o flag and the outputname.

E.g. -ohello.o doesn't compile, -o hello.o makes no problems.

In the properties page of the project i didn't find a way to solve this
problem.

Is there any way, to tell the Makefile-Generator to add an blank after
the -o flag?

Thanks in advance
Marcus
Re: adding a blank between -o and the outputname [message #154184 is a reply to message #153508] Thu, 15 September 2005 01:48 Go to previous message
Eclipse UserFriend
Originally posted by: dsterling.somalogic.com

Marcus Wagner wrote:

> Hi @ all

> i have a problem under 2 sparc solaris machines.

> Im working with Eclipse 3.1, CDT 3.0 on sparc solaris 9/10, using the
> managed make mechanism.

> The assembler as (even with SUNStudio 10 Update 1) needs an blank
> between the -o flag and the outputname.

> E.g. -ohello.o doesn't compile, -o hello.o makes no problems.

> In the properties page of the project i didn't find a way to solve this
> problem.

> Is there any way, to tell the Makefile-Generator to add an blank after
> the -o flag?

> Thanks in advance
> Marcus

Hi Marcus. I just went through a similar nightmare under OS X( gcc 3.3
likes a space between the "-o" and the output filename too !) I am a new
eclipse user, and even newer to CDT, but maybe my experience with OS X
will help you.

Have a look at the plugin.xml file in
Eclipse-3.1/plugins/org.eclipse.cdt.managedbuilder.gnu.ui_3. 0.0 directory.
I won't pretend that I understand the contents of this file, but you
probably want to locate the outputFlag field for the tool specified for
your SPARC system and replace the "-o" with the appropriate flag. For the
gcc compiler under OS X I used outputFlag="--output=" for the linker.macos
tool and that fixed the whitespace issue for me. It wasn't immediately
obvious to me which tool is being used on the Sparc -- probably
'linker.gnu.c' ... unless you get feedback from a more knowledgable source
you'll have to resort to trial-n-error to figure out which tool
configuration to diddle.

Once you edit plugin.xml you might have to restart eclipse with the -clean
flag on the command line to force it to re-read the xml file. This seems
to work under OS X but your mileage may vary.

Apparently eclipse remembers the build settings for each project (surely
there is a way to force it to refresh these, but I haven't figured that
out yet), so you may have to re-create the offending project (just add a
new C++ project and drag over all the source files) before the changes in
the xml file will take effect.


David
Previous Topic:Programmatically applying code templates
Next Topic:Step Over in debugger
Goto Forum:
  


Current Time: Sat May 10 11:25:37 EDT 2025

Powered by FUDForum. Page generated in 0.02593 seconds
.:: Contact :: Home ::.

Powered by: FUDforum 3.0.2.
Copyright ©2001-2010 FUDforum Bulletin Board Software

Back to the top