Skip to main content



      Home
Home » Language IDEs » C / C++ IDE (CDT) » running make in directory outside the project
running make in directory outside the project [message #151093] Fri, 12 August 2005 11:45 Go to next message
Eclipse UserFriend
Originally posted by: michal.schulz.gmx.de

Hello.

I'm new and quite happy user of eclipse and CDT. I have only one problem.

The project I work on is quite big (180MB approximatelly) with tons of
files. If I would turn indexing on, eclipse would need ages to go through
all files and index them. Also, updating project after build is awfully
slow.

Due to nature of this project, I can work on one of modules only, and thus
keep the ability of indexing and fast responsivity of eclipse. However, I
have to tell eclipse that the project directory resides somewhere within my
big project.

Can I force eclipse to start makefile in specified directory, whereas the
directory is outside the project managed by eclipse?

Regards,
Michal.
Re: running make in directory outside the project [message #151103 is a reply to message #151093] Fri, 12 August 2005 14:40 Go to previous messageGo to next message
Eclipse UserFriend
Originally posted by: alexfarberov.[nospam]hotmail.com

Not sure about how to do it in a managed build.. perhaps a developer
could answer that. I can propose a workaround - checkout from cvs not
the whole project but only the module that you need into a new c++
project. That way you can have separate eclipse projects for each of
your modules and managed builds should work fine..

FYI, the ctags indexer is very fast and works well on huge projects.

Michal Schulz wrote:
> Hello.
>
> I'm new and quite happy user of eclipse and CDT. I have only one problem.
>
> The project I work on is quite big (180MB approximatelly) with tons of
> files. If I would turn indexing on, eclipse would need ages to go through
> all files and index them. Also, updating project after build is awfully
> slow.
>
> Due to nature of this project, I can work on one of modules only, and thus
> keep the ability of indexing and fast responsivity of eclipse. However, I
> have to tell eclipse that the project directory resides somewhere within my
> big project.
>
> Can I force eclipse to start makefile in specified directory, whereas the
> directory is outside the project managed by eclipse?
>
> Regards,
> Michal.
>
Re: running make in directory outside the project [message #151110 is a reply to message #151103] Fri, 12 August 2005 16:11 Go to previous messageGo to next message
Eclipse UserFriend
Originally posted by: michal.schulz.gmx.de

Alex Farberov wrote:

> Not sure about how to do it in a managed build.. perhaps a developer
> could answer that. I can propose a workaround - checkout from cvs not
> the whole project but only the module that you need into a new c++
> project. That way you can have separate eclipse projects for each of
> your modules and managed builds should work fine..

I may do that, but unfortunatelly, do to the construction of build system in
this project, I need whole tree. It is so, because make has to be launched
in root directory of complete project. Running make inside of one of
module's directories will not work.

> FYI, the ctags indexer is very fast and works well on huge projects.

Yes, but it spends at least one minute on "refreshing project" after each
project build. It's way to long.

regards,
Michal.
Re: running make in directory outside the project [message #151127 is a reply to message #151093] Sun, 14 August 2005 15:29 Go to previous messageGo to next message
Eclipse UserFriend
Michal Schulz wrote:
> Hello.
>
> I'm new and quite happy user of eclipse and CDT. I have only one problem.
>
> The project I work on is quite big (180MB approximatelly) with tons of
> files. If I would turn indexing on, eclipse would need ages to go through
> all files and index them. Also, updating project after build is awfully
> slow.
>
> Due to nature of this project, I can work on one of modules only, and thus
> keep the ability of indexing and fast responsivity of eclipse. However, I
> have to tell eclipse that the project directory resides somewhere within my
> big project.
>
> Can I force eclipse to start makefile in specified directory, whereas the
> directory is outside the project managed by eclipse?
>
> Regards,
> Michal.
>
That's what I'm doing in my environment. If you are not using "managed
make" (and since working with big "legacy" project I assume you don't)
you can specify any build command you like.
I'm using something like this as a build command:
make -C /my_home_dir/root_of_my_project -f our_very_fat_makefile
Than in fields that specify targets for building, rebuilding and
cleaning I specify targets from the fat_makefile related to my module.
Regards,
CK
Re: running make in directory outside the project [message #151143 is a reply to message #151127] Sun, 14 August 2005 17:36 Go to previous messageGo to next message
Eclipse UserFriend
Originally posted by: michal.schulz.gmx.de

Czerwony Kapturek wrote:

> That's what I'm doing in my environment. If you are not using "managed
> make" (and since working with big "legacy" project I assume you don't)
> you can specify any build command you like.
> I'm using something like this as a build command:
> make -C /my_home_dir/root_of_my_project -f our_very_fat_makefile

Thanks!

I've never thought that the solution might be so simple :)

regards,
M.
Re: running make in directory outside the project [message #151339 is a reply to message #151143] Wed, 17 August 2005 05:08 Go to previous message
Eclipse UserFriend
Michal Schulz wrote:
> Czerwony Kapturek wrote:
>
>
>>That's what I'm doing in my environment. If you are not using "managed
>>make" (and since working with big "legacy" project I assume you don't)
>>you can specify any build command you like.
>>I'm using something like this as a build command:
>>make -C /my_home_dir/root_of_my_project -f our_very_fat_makefile
>
>
> Thanks!
>
> I've never thought that the solution might be so simple :)
>
> regards,
> M.
>
You are welcome.
One more tip: when specifying path to the maim makefile you could use
${project_loc} variable and path relative to your .project. Saves some
time when working on multiple source trees.
CK
Previous Topic:how to use pkg-config to pass options to compiler?
Next Topic:CDT 2.1.1 on AIX version cannot debug or run
Goto Forum:
  


Current Time: Fri May 09 14:24:28 EDT 2025

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

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

Back to the top