| C/C++ project problem [message #179726] |
Tue, 14 November 2006 15:20  |
Eclipse User |
|
|
|
Originally posted by: matsblide.hotmail.com
Hi,
I have put together my first managed make C/C++ project in Eclips with a
bunch of .C and .S files. When I build, the .C files seams to compile
allright and the linker links but with some errors because the .S files
has not been assembled - why? Is my question.
I also notice that my c files are shown as textfiles in the project
navigator dispite that the global file type setting says that *.c files is
C files. The assemmbly files in the project are recognised as assemmbly
files. The C files on the otherhand are compiled as C files but the
assembly files are not assembled!?!? Confusing? Yes!
Btw. isn't there any way that one can import available make files so that
I don't have to configure the whole project from scratch?
Any help apreciated!
Rgds,
Mats
|
|
|
|
| Re: C/C++ project problem [message #179792 is a reply to message #179750] |
Wed, 15 November 2006 02:48  |
| Eclipse User |
|
|
|
Originally posted by: dmsubs.NOSPAM.consertum.com
By default, the managed make system uses GNU tools (i.e. gcc). You can rename
the tools used for a project by editing the project properties (i.e.
arm-none-eabi-gcc).
Alternatively, you can create a plugin that defines a new project type that
supports your particular tools (not necessarily GNU). See the Managed Build
System Extensibility document for details. Note that you do not need to write
any Java for this - it is all XML.
--
Derek
Ray Hurst wrote:
> Mats,
> Sorry that this isn't an answer to your question.
> However, I would check to see if the GNU assembler is loaded on your
> machine, as.exe.
>
> I am also interseted in the answer here.
> I see from the documentation that the Managed Make is a plug-in that
> apparently builds the makefile and all of its dependencies.
> It appears to be hardcoded to only use the GNU tools.
>
> Soooo...
> How does the managed make plug-in source files and invoke the proper
> assembler, C++ compiler etc.
> I see from the docs that for the Standard make it is up to the user to
> create the makefile and invoke the correct tools for the job.
> This is how cross-compilers can be run.
> Ray Hurst
>
> "Mats Blide" <matsblide@hotmail.com> wrote in message
> news:657f384665265a6153114b428f5c1f92$1@www.eclipse.org...
>> Hi,
>>
>> I have put together my first managed make C/C++ project in Eclips with a
>> bunch of .C and .S files. When I build, the .C files seams to compile
>> allright and the linker links but with some errors because the .S files
>> has not been assembled - why? Is my question.
>> I also notice that my c files are shown as textfiles in the project
>> navigator dispite that the global file type setting says that *.c files is
>> C files. The assemmbly files in the project are recognised as assemmbly
>> files. The C files on the otherhand are compiled as C files but the
>> assembly files are not assembled!?!? Confusing? Yes!
>>
>> Btw. isn't there any way that one can import available make files so that
>> I don't have to configure the whole project from scratch?
>>
>>
>> Any help apreciated!
>>
>> Rgds,
>> Mats
>>
>
>
|
|
|
|
|
|
| Re: C/C++ project problem [message #179868 is a reply to message #179860] |
Wed, 15 November 2006 11:22 |
| Eclipse User |
|
|
|
Originally posted by: dmsubs.NOSPAM.consertum.com
Note that you are not renaming anything. The 'plain' executables are supplied
alongside the 'prefix' executables. For example:
..../gnu/bin/arm-none-eabi-gcc.exe is also supplied as
..../gnu/arm-none-eabi/bin/gcc.exe
So changing your path will pick up the plain executables.
Anyway, to change the compiler name, you don't need to write any Java. To do
this in the approved way, you write a plugin.xml file. See The Managed Build
System Extensibility document (it is supplied in your CDT documentation if you
have installed the SDK feature. If not, google for it).
You can find the plugin.xml that supports the GNU tools by unzipping
org.eclipse.cdt.managedbuilder.gnu.ui.*.jar (a jar is a zip file)
HTH
--
Derek
Michael Schnell wrote:
> Derek Morris wrote:
>> That is correct.
>>
>> However, you could add path/to/gnu/tools/arm-none-eabi/bin to you path
>> (instead of path/to/gnu/tools/bin) as there is gcc.exe located in there.
>>
> Not a good way, IMHO.
>
> The GNU cross tools are named by GNU with that prefix for some purpose,
> I suppose, so who are we to rename them.
>
> When doing a make file for cross compiling you usually manage this by
> enhancing the $(CC) environment variable by the prefix in the most outer
> make script. This is what Eclipse should do as well.
>
> I fear that you will need to modify GnuMakefileGenerator.java on that
> behalf, but doing Java is beyond my scope :(
>
> -Michael
|
|
|
| Re: C/C++ project problem [message #179876 is a reply to message #179868] |
Wed, 15 November 2006 13:42 |
| Eclipse User |
|
|
|
Derek,
Thanks for your response.
I agree with you on the build of gnu tools.
GNU does build multiple paths to the same tool binaries.
Your info has opened quite a few doors of learning to catch up on.
I noticed the CDT DOM link in the SDK appears to be broken.
Is this correct or do I have a corrupted copy?
Ray
"Derek Morris" <dmsubs@NOSPAM.consertum.com> wrote in message
news:ejfes7$md3$1@utils.eclipse.org...
> Note that you are not renaming anything. The 'plain' executables are
> supplied alongside the 'prefix' executables. For example:
>
> .../gnu/bin/arm-none-eabi-gcc.exe is also supplied as
> .../gnu/arm-none-eabi/bin/gcc.exe
>
> So changing your path will pick up the plain executables.
>
> Anyway, to change the compiler name, you don't need to write any Java. To
> do this in the approved way, you write a plugin.xml file. See The Managed
> Build System Extensibility document (it is supplied in your CDT
> documentation if you have installed the SDK feature. If not, google for
> it).
>
> You can find the plugin.xml that supports the GNU tools by unzipping
> org.eclipse.cdt.managedbuilder.gnu.ui.*.jar (a jar is a zip file)
>
> HTH
> --
> Derek
>
>
> Michael Schnell wrote:
>> Derek Morris wrote:
>>> That is correct.
>>>
>>> However, you could add path/to/gnu/tools/arm-none-eabi/bin to you path
>>> (instead of path/to/gnu/tools/bin) as there is gcc.exe located in there.
>>>
>> Not a good way, IMHO.
>>
>> The GNU cross tools are named by GNU with that prefix for some purpose, I
>> suppose, so who are we to rename them.
>>
>> When doing a make file for cross compiling you usually manage this by
>> enhancing the $(CC) environment variable by the prefix in the most outer
>> make script. This is what Eclipse should do as well.
>>
>> I fear that you will need to modify GnuMakefileGenerator.java on that
>> behalf, but doing Java is beyond my scope :(
>>
>> -Michael
|
|
|
Powered by
FUDForum. Page generated in 0.03986 seconds
Home