I tried what you suggested, and it did not work for me on my cygwin
development system.
I generally do not like making projects dependent on env vars, since
its just more more step to forget if I need to reproduce the
development system. The .project files of eclipse are portable.
--- In ts-7000%40yahoogroups.com, "Dustin Oprea" <> wrote:
>
> OK, Dudes:
>
>
> There is only one place you have to change the path. I'm not talking
about
> changing it for the system-- I'm just talking about adding an
environment
> just for the project. Go to the project's properties, C/C++ Build ->
> Environment, and add a variable named "path" with value
"${PATH}:<crosstool
> directory>". This will cause the path value to contain the crosstool
just
> for the build.
>
> To add the include and library paths, go to the project's
properties, C/C++
> General -> Paths and Symbols -> <"Includes" or "Library paths"> tab.
>
> To add specific libraries, go to the project's properties, C/C++
Build ->
> Settings -> Tool settings tab -> GCC C++ Linker -> Libraries, and
add the
> library names ("pthread" and "rt", for example). I recommended,
before, that
> the libraries be statically linked to reduce the initial complexity
of the
> process (you can work on making them shared, later)-- You can do
this in the
> linker's "Miscellaneous" tab and added "-static" to the "Linker flags"
> text-field.
>
>
> In my situation, I use an Ubuntu station for development (x86), and then
> have the ability to build for ARM. I have three projects: All of my
> sourcecode is in a library project. I just needed it in one place that I
> won't ever compile directly for reasons I'll soon show, and a library
> project seemed good so I could be sure I never accidentally compiled the
> code to an executable there.
>
> Then, I set-up a project for my ARM and Intel executables, neither
of which
> have files. I then went to the project settings of both and, under
"Paths
> and Symbols" under the C/C++ General lefthand-side item and then
under the
> "Source location" tab, I clicked on "Add workspace folder" and added the
> main source directory from the library-project I mentioned above.
Once I did
> this for both, I went under the ARM project and make sure the tool
paths and
> names were correct for the crosstool package (including the path
entry under
> the environment).
>
> What the above allows me to do is to click on either the Intel or ARM
> projects and build using the same codebase, which are stored in a
unified
> manner under the library project.
>
>
> It's worth mentioning that the linked source-code will appear
underneath the
> two projects, which will give you three separate places that the
source code
> may be found. However, if you have three copies of one of the files
open and
> then edit one, all three open copies will reflect the changes upon
saving
> the file.
>
>
> You can look up this information on Eclipse's CDT support site.
>
>
> Dustin Oprea
>
>
> On 1/20/08, mrjbradski <> wrote:
> >
> > 1) project properties.c/c++ build.settings.directories - i have this
> > set to:
> >
> > /opt/crosstool/gcc-3.3.4-glibc-2.3.2
> > /arm-unknown-linux-gnu/arm-unknown-linux-gnu/include
> >
> > 2) project properties.c linker.settings.library search path - i have
> > this set to:
> >
> > /opt/crosstool/gcc-3.3.4-glibc-2.3.2
> > /arm-unknown-linux-gnu/arm-unknown-linux-gnu/lib
> >
> >
> >
>
>
>
> --
>
> Dustin Oprea
>
> Software Engineer
> Intrepid Control Systems
> (1+) 248-726-0605
>