Home » Language IDEs » C / C++ IDE (CDT) » Multiple projects on common src directory
| Multiple projects on common src directory [message #151521] |
Thu, 18 August 2005 17:03  |
Eclipse User |
|
|
|
Originally posted by: eclipse.dharty.com
Hello,
Are there any plans to allow multiple Eclipse projects to work on a
common code base?
We have a need to be able to build multiple projects with different
tools (eg M$ compiler, Embedded compilers) on a common code base.
For example we have no less than four different applications with all of
their code stuffed in a common source directory. Alot of the code is
shared with extensive use of #ifdefs (legacy design).
Right now most of the developers in our group use Visual Studio. In VS,
a "Solution" is like a "Workspace" and can contain many projects.
However, source files for each project do not need to reside in the
projects folder hierachy and are selected individually from anywhere on
the filesystem. Like Eclipse, each project can be assigned different
preprocessor compiles, and different build commands.
Contrast that with an Eclipse workspace; multiple projects each with a
unique source directory which by default include ALL of the code in that
directory.
Are their any capabilities for Eclipse planned that would let you
specify individual files to include in a project from source directories
that are not in the projects folder?
I relize in *nix land one could create a project folder and then create
links to the source folder (ln -s ../src/), but that obviously wont work
in windows.
Here is a sample layout of our workspace:
workspace\
workspace\.*project << single eclipse project
src\*.[ch]*
projects\StudioSolution.sln
projects\project1.vcproj << includes selected files from src
projects\project2.vcproj << includes selected files from src
....
projects\projectn.vcproj << includes selected files from src
projects\buildscript[1-n].bat
I have an eclipse project in workspace so that I can build the most
often used of the projects listed above, but in order for the indexer to
work correctly, I have to set the #defines for this project alone and
manually exclude the many files that I don't want indexed (don't belong
to the build). I could set up additional make targets to build the
other projects, but the files for those projects don't get indexed so I
lose out on features like code insite. If I don't exclude the files,
the indexer literrally give me thousands of warnings ranging from #def
warnings to preprocessor inclusion warnings (#include).
If I want to work on any of the other projects I have to open up Visual
Studio and work from there. Once VS is open, I can build all of the
projects and end up not returning to Eclipse.
Thanks,
David
|
|
|
| Re: Multiple projects on common src directory [message #151539 is a reply to message #151521] |
Fri, 19 August 2005 04:25  |
| Eclipse User |
|
|
|
Originally posted by: doug-list.threepenny.net
Hi David,
I'm not sure what the approved approach for this is, but one solution is
to create separate folders for each Eclipse project (outside of your src
tree) and then use the Project | Properties | Project Paths | Source tab
(gee--how could you miss that :) to manually add your 'src' folder to
each Eclipse project.
You'll also find the ability to exclude folders and do other nice things
here that get you away from the "everything under X must be in the
project" model. You can even go down to the file level if you wish, a
la Visual Studio.
I haven't tried this approach on a CDT project but I've used it with
success on Java projects.
Doug
David H wrote:
>
> Hello,
>
> Are there any plans to allow multiple Eclipse projects to work on a
> common code base?
>
> We have a need to be able to build multiple projects with different
> tools (eg M$ compiler, Embedded compilers) on a common code base.
>
> For example we have no less than four different applications with all of
> their code stuffed in a common source directory. Alot of the code is
> shared with extensive use of #ifdefs (legacy design).
>
> Right now most of the developers in our group use Visual Studio. In VS,
> a "Solution" is like a "Workspace" and can contain many projects.
> However, source files for each project do not need to reside in the
> projects folder hierachy and are selected individually from anywhere on
> the filesystem. Like Eclipse, each project can be assigned different
> preprocessor compiles, and different build commands.
>
> Contrast that with an Eclipse workspace; multiple projects each with a
> unique source directory which by default include ALL of the code in that
> directory.
>
> Are their any capabilities for Eclipse planned that would let you
> specify individual files to include in a project from source directories
> that are not in the projects folder?
>
> I relize in *nix land one could create a project folder and then create
> links to the source folder (ln -s ../src/), but that obviously wont work
> in windows.
>
> Here is a sample layout of our workspace:
>
> workspace\
> workspace\.*project << single eclipse project
> src\*.[ch]*
> projects\StudioSolution.sln
> projects\project1.vcproj << includes selected files from src
> projects\project2.vcproj << includes selected files from src
> ...
> projects\projectn.vcproj << includes selected files from src
> projects\buildscript[1-n].bat
>
>
> I have an eclipse project in workspace so that I can build the most
> often used of the projects listed above, but in order for the indexer to
> work correctly, I have to set the #defines for this project alone and
> manually exclude the many files that I don't want indexed (don't belong
> to the build). I could set up additional make targets to build the
> other projects, but the files for those projects don't get indexed so I
> lose out on features like code insite. If I don't exclude the files,
> the indexer literrally give me thousands of warnings ranging from #def
> warnings to preprocessor inclusion warnings (#include).
>
> If I want to work on any of the other projects I have to open up Visual
> Studio and work from there. Once VS is open, I can build all of the
> projects and end up not returning to Eclipse.
>
> Thanks,
>
> David
|
|
|
| Re: Multiple projects on common src directory [message #152659 is a reply to message #151539] |
Tue, 30 August 2005 17:42 |
| Eclipse User |
|
|
|
Originally posted by: eclipse.dharty.com
> to create separate folders for each Eclipse project (outside of your
s rc tree)
I think that works in the java jdt, but in the cdt the only "folders"
available to you are those that are on the same path as your project. eg
c:\eclipseProject\.*project
c:\eclipseProject\src (this can be made a "source" directory
c:\otherPath\src (this cannot)
Thanks though,
David
Doug Pearson wrote:
> Hi David,
>
> I'm not sure what the approved approach for this is, but one solution is
> to create separate folders for each Eclipse project (outside of your src
> tree) and then use the Project | Properties | Project Paths | Source tab
> (gee--how could you miss that :) to manually add your 'src' folder to
> each Eclipse project.
>
> You'll also find the ability to exclude folders and do other nice things
> here that get you away from the "everything under X must be in the
> project" model. You can even go down to the file level if you wish, a
> la Visual Studio.
>
> I haven't tried this approach on a CDT project but I've used it with
> success on Java projects.
>
> Doug
>
> David H wrote:
>
>>
>> Hello,
>>
>> Are there any plans to allow multiple Eclipse projects to work on a
>> common code base?
>>
>> We have a need to be able to build multiple projects with different
>> tools (eg M$ compiler, Embedded compilers) on a common code base.
>>
>> For example we have no less than four different applications with all
>> of their code stuffed in a common source directory. Alot of the code
>> is shared with extensive use of #ifdefs (legacy design).
>>
>> Right now most of the developers in our group use Visual Studio. In
>> VS, a "Solution" is like a "Workspace" and can contain many projects.
>> However, source files for each project do not need to reside in the
>> projects folder hierachy and are selected individually from anywhere
>> on the filesystem. Like Eclipse, each project can be assigned
>> different preprocessor compiles, and different build commands.
>>
>> Contrast that with an Eclipse workspace; multiple projects each with a
>> unique source directory which by default include ALL of the code in
>> that directory.
>>
>> Are their any capabilities for Eclipse planned that would let you
>> specify individual files to include in a project from source
>> directories that are not in the projects folder?
>>
>> I relize in *nix land one could create a project folder and then
>> create links to the source folder (ln -s ../src/), but that obviously
>> wont work in windows.
>>
>> Here is a sample layout of our workspace:
>>
>> workspace\
>> workspace\.*project << single eclipse project
>> src\*.[ch]*
>> projects\StudioSolution.sln
>> projects\project1.vcproj << includes selected files from src
>> projects\project2.vcproj << includes selected files from src
>> ...
>> projects\projectn.vcproj << includes selected files from src
>> projects\buildscript[1-n].bat
>>
>>
>> I have an eclipse project in workspace so that I can build the most
>> often used of the projects listed above, but in order for the indexer
>> to work correctly, I have to set the #defines for this project alone
>> and manually exclude the many files that I don't want indexed (don't
>> belong to the build). I could set up additional make targets to build
>> the other projects, but the files for those projects don't get indexed
>> so I lose out on features like code insite. If I don't exclude the
>> files, the indexer literrally give me thousands of warnings ranging
>> from #def warnings to preprocessor inclusion warnings (#include).
>>
>> If I want to work on any of the other projects I have to open up
>> Visual Studio and work from there. Once VS is open, I can build all
>> of the projects and end up not returning to Eclipse.
>>
>> Thanks,
>>
>> David
>
>
|
|
|
| Re: Multiple projects on common src directory [message #153060 is a reply to message #152659] |
Fri, 02 September 2005 17:00 |
| Eclipse User |
|
|
|
Originally posted by: cchapin.googleNOSPAM.com
It does work with CDT, but it's easy to miss:
1. Navigate to the Project | Properties | Project Paths | Source tab as
described by Doug.
2. Click "Add Folder". A "Source Folder Selection" window pops up.
3. Click "Create New Folder". A "New Folder" window pops up.
4. Here's the part you probably missed: Click "Advanced". The New Folder
popup expands with an option to link to an [existing] folder in the file system.
Now you can refer to any folder you want.
Chip
David H wrote:
> > to create separate folders for each Eclipse project (outside of your
> src tree)
>
> I think that works in the java jdt, but in the cdt the only "folders"
> available to you are those that are on the same path as your project. eg
>
> c:\eclipseProject\.*project
> c:\eclipseProject\src (this can be made a "source" directory
>
> c:\otherPath\src (this cannot)
>
> Thanks though,
>
> David
>
>
>
>
> Doug Pearson wrote:
>
>> Hi David,
>>
>> I'm not sure what the approved approach for this is, but one solution
>> is to create separate folders for each Eclipse project (outside of
>> your src tree) and then use the Project | Properties | Project Paths |
>> Source tab (gee--how could you miss that :) to manually add your 'src'
>> folder to each Eclipse project.
>>
>> You'll also find the ability to exclude folders and do other nice
>> things here that get you away from the "everything under X must be in
>> the project" model. You can even go down to the file level if you
>> wish, a la Visual Studio.
>>
>> I haven't tried this approach on a CDT project but I've used it with
>> success on Java projects.
>>
>> Doug
>>
>> David H wrote:
>>
>>>
>>> Hello,
>>>
>>> Are there any plans to allow multiple Eclipse projects to work on a
>>> common code base?
>>>
>>> We have a need to be able to build multiple projects with different
>>> tools (eg M$ compiler, Embedded compilers) on a common code base.
>>>
>>> For example we have no less than four different applications with all
>>> of their code stuffed in a common source directory. Alot of the code
>>> is shared with extensive use of #ifdefs (legacy design).
>>>
>>> Right now most of the developers in our group use Visual Studio. In
>>> VS, a "Solution" is like a "Workspace" and can contain many projects.
>>> However, source files for each project do not need to reside in the
>>> projects folder hierachy and are selected individually from anywhere
>>> on the filesystem. Like Eclipse, each project can be assigned
>>> different preprocessor compiles, and different build commands.
>>>
>>> Contrast that with an Eclipse workspace; multiple projects each with
>>> a unique source directory which by default include ALL of the code in
>>> that directory.
>>>
>>> Are their any capabilities for Eclipse planned that would let you
>>> specify individual files to include in a project from source
>>> directories that are not in the projects folder?
>>>
>>> I relize in *nix land one could create a project folder and then
>>> create links to the source folder (ln -s ../src/), but that obviously
>>> wont work in windows.
>>>
>>> Here is a sample layout of our workspace:
>>>
>>> workspace\
>>> workspace\.*project << single eclipse project
>>> src\*.[ch]*
>>> projects\StudioSolution.sln
>>> projects\project1.vcproj << includes selected files from src
>>> projects\project2.vcproj << includes selected files from src
>>> ...
>>> projects\projectn.vcproj << includes selected files from src
>>> projects\buildscript[1-n].bat
>>>
>>>
>>> I have an eclipse project in workspace so that I can build the most
>>> often used of the projects listed above, but in order for the indexer
>>> to work correctly, I have to set the #defines for this project alone
>>> and manually exclude the many files that I don't want indexed (don't
>>> belong to the build). I could set up additional make targets to
>>> build the other projects, but the files for those projects don't get
>>> indexed so I lose out on features like code insite. If I don't
>>> exclude the files, the indexer literrally give me thousands of
>>> warnings ranging from #def warnings to preprocessor inclusion
>>> warnings (#include).
>>>
>>> If I want to work on any of the other projects I have to open up
>>> Visual Studio and work from there. Once VS is open, I can build all
>>> of the projects and end up not returning to Eclipse.
>>>
>>> Thanks,
>>>
>>> David
>>
>>
>>
|
|
| |
| Re: Multiple projects on common src directory [message #153919 is a reply to message #153060] |
Tue, 13 September 2005 22:58 |
| Eclipse User |
|
|
|
Originally posted by: fireonyoursleeve.hotmail.com
This appears to only work for standard make projects, not managed make. The
ability to exclude directories in managed projects would be pretty nice.
(unless I'm missing something)
"Chip Chapin" <cchapin@googleNOSPAM.com> wrote in message
news:dfa0eu$7vq$1@news.eclipse.org...
> It does work with CDT, but it's easy to miss:
>
> 1. Navigate to the Project | Properties | Project Paths | Source tab as
> described by Doug.
> 2. Click "Add Folder". A "Source Folder Selection" window pops up.
> 3. Click "Create New Folder". A "New Folder" window pops up.
> 4. Here's the part you probably missed: Click "Advanced". The New
> Folder popup expands with an option to link to an [existing] folder in the
> file system. Now you can refer to any folder you want.
>
> Chip
>
>
> David H wrote:
>> > to create separate folders for each Eclipse project (outside of your
>> src tree)
>>
>> I think that works in the java jdt, but in the cdt the only "folders"
>> available to you are those that are on the same path as your project. eg
>>
>> c:\eclipseProject\.*project
>> c:\eclipseProject\src (this can be made a "source" directory
>>
>> c:\otherPath\src (this cannot)
>>
>> Thanks though,
>>
>> David
>>
>>
>>
>>
>> Doug Pearson wrote:
>>
>>> Hi David,
>>>
>>> I'm not sure what the approved approach for this is, but one solution is
>>> to create separate folders for each Eclipse project (outside of your src
>>> tree) and then use the Project | Properties | Project Paths | Source tab
>>> (gee--how could you miss that :) to manually add your 'src' folder to
>>> each Eclipse project.
>>>
>>> You'll also find the ability to exclude folders and do other nice things
>>> here that get you away from the "everything under X must be in the
>>> project" model. You can even go down to the file level if you wish, a
>>> la Visual Studio.
>>>
>>> I haven't tried this approach on a CDT project but I've used it with
>>> success on Java projects.
>>>
>>> Doug
>>>
>>> David H wrote:
>>>
>>>>
>>>> Hello,
>>>>
>>>> Are there any plans to allow multiple Eclipse projects to work on a
>>>> common code base?
>>>>
>>>> We have a need to be able to build multiple projects with different
>>>> tools (eg M$ compiler, Embedded compilers) on a common code base.
>>>>
>>>> For example we have no less than four different applications with all
>>>> of their code stuffed in a common source directory. Alot of the code
>>>> is shared with extensive use of #ifdefs (legacy design).
>>>>
>>>> Right now most of the developers in our group use Visual Studio. In
>>>> VS, a "Solution" is like a "Workspace" and can contain many projects.
>>>> However, source files for each project do not need to reside in the
>>>> projects folder hierachy and are selected individually from anywhere on
>>>> the filesystem. Like Eclipse, each project can be assigned different
>>>> preprocessor compiles, and different build commands.
>>>>
>>>> Contrast that with an Eclipse workspace; multiple projects each with a
>>>> unique source directory which by default include ALL of the code in
>>>> that directory.
>>>>
>>>> Are their any capabilities for Eclipse planned that would let you
>>>> specify individual files to include in a project from source
>>>> directories that are not in the projects folder?
>>>>
>>>> I relize in *nix land one could create a project folder and then create
>>>> links to the source folder (ln -s ../src/), but that obviously wont
>>>> work in windows.
>>>>
>>>> Here is a sample layout of our workspace:
>>>>
>>>> workspace\
>>>> workspace\.*project << single eclipse project
>>>> src\*.[ch]*
>>>> projects\StudioSolution.sln
>>>> projects\project1.vcproj << includes selected files from src
>>>> projects\project2.vcproj << includes selected files from src
>>>> ...
>>>> projects\projectn.vcproj << includes selected files from src
>>>> projects\buildscript[1-n].bat
>>>>
>>>>
>>>> I have an eclipse project in workspace so that I can build the most
>>>> often used of the projects listed above, but in order for the indexer
>>>> to work correctly, I have to set the #defines for this project alone
>>>> and manually exclude the many files that I don't want indexed (don't
>>>> belong to the build). I could set up additional make targets to build
>>>> the other projects, but the files for those projects don't get indexed
>>>> so I lose out on features like code insite. If I don't exclude the
>>>> files, the indexer literrally give me thousands of warnings ranging
>>>> from #def warnings to preprocessor inclusion warnings (#include).
>>>>
>>>> If I want to work on any of the other projects I have to open up Visual
>>>> Studio and work from there. Once VS is open, I can build all of the
>>>> projects and end up not returning to Eclipse.
>>>>
>>>> Thanks,
>>>>
>>>> David
>>>
>>>
>>>
|
|
|
| Re: Multiple projects on common src directory [message #155921 is a reply to message #153060] |
Fri, 07 October 2005 23:25 |
| Eclipse User |
|
|
|
Originally posted by: eclipse.dharty.com
Awesome.
There is still a slight problem with this. The project path must be
absolute (on windows anyway). This means I cannot check the project into
revision control without some modification by the user on checkout.
I did create a "PROJECT_ROOT" variable set to c:\flightsw when I was
adding the folder. This variable can be changed on checkout, but it
would have been nice if I could have set the path relatively such as
..\src
instead of
c:\flightsw\src
Thanks for the info though.
David
Chip Chapin wrote:
> It does work with CDT, but it's easy to miss:
>
> 1. Navigate to the Project | Properties | Project Paths | Source tab
> as described by Doug.
> 2. Click "Add Folder". A "Source Folder Selection" window pops up.
> 3. Click "Create New Folder". A "New Folder" window pops up.
> 4. Here's the part you probably missed: Click "Advanced". The New
> Folder popup expands with an option to link to an [existing] folder in
> the file system. Now you can refer to any folder you want.
>
> Chip
>
>
> David H wrote:
>
>> > to create separate folders for each Eclipse project (outside of
>> your src tree)
>>
>> I think that works in the java jdt, but in the cdt the only "folders"
>> available to you are those that are on the same path as your project. eg
>>
>> c:\eclipseProject\.*project
>> c:\eclipseProject\src (this can be made a "source" directory
>>
>> c:\otherPath\src (this cannot)
>>
>> Thanks though,
>>
>> David
>>
>>
>>
>>
>> Doug Pearson wrote:
>>
>>> Hi David,
>>>
>>> I'm not sure what the approved approach for this is, but one solution
>>> is to create separate folders for each Eclipse project (outside of
>>> your src tree) and then use the Project | Properties | Project Paths
>>> | Source tab (gee--how could you miss that :) to manually add your
>>> 'src' folder to each Eclipse project.
>>>
>>> You'll also find the ability to exclude folders and do other nice
>>> things here that get you away from the "everything under X must be in
>>> the project" model. You can even go down to the file level if you
>>> wish, a la Visual Studio.
>>>
>>> I haven't tried this approach on a CDT project but I've used it with
>>> success on Java projects.
>>>
>>> Doug
>>>
>>> David H wrote:
>>>
>>>>
>>>> Hello,
>>>>
>>>> Are there any plans to allow multiple Eclipse projects to work on a
>>>> common code base?
>>>>
>>>> We have a need to be able to build multiple projects with different
>>>> tools (eg M$ compiler, Embedded compilers) on a common code base.
>>>>
>>>> For example we have no less than four different applications with
>>>> all of their code stuffed in a common source directory. Alot of the
>>>> code is shared with extensive use of #ifdefs (legacy design).
>>>>
>>>> Right now most of the developers in our group use Visual Studio. In
>>>> VS, a "Solution" is like a "Workspace" and can contain many
>>>> projects. However, source files for each project do not need to
>>>> reside in the projects folder hierachy and are selected individually
>>>> from anywhere on the filesystem. Like Eclipse, each project can be
>>>> assigned different preprocessor compiles, and different build commands.
>>>>
>>>> Contrast that with an Eclipse workspace; multiple projects each with
>>>> a unique source directory which by default include ALL of the code
>>>> in that directory.
>>>>
>>>> Are their any capabilities for Eclipse planned that would let you
>>>> specify individual files to include in a project from source
>>>> directories that are not in the projects folder?
>>>>
>>>> I relize in *nix land one could create a project folder and then
>>>> create links to the source folder (ln -s ../src/), but that
>>>> obviously wont work in windows.
>>>>
>>>> Here is a sample layout of our workspace:
>>>>
>>>> workspace\
>>>> workspace\.*project << single eclipse project
>>>> src\*.[ch]*
>>>> projects\StudioSolution.sln
>>>> projects\project1.vcproj << includes selected files from src
>>>> projects\project2.vcproj << includes selected files from src
>>>> ...
>>>> projects\projectn.vcproj << includes selected files from src
>>>> projects\buildscript[1-n].bat
>>>>
>>>>
>>>> I have an eclipse project in workspace so that I can build the most
>>>> often used of the projects listed above, but in order for the
>>>> indexer to work correctly, I have to set the #defines for this
>>>> project alone and manually exclude the many files that I don't want
>>>> indexed (don't belong to the build). I could set up additional make
>>>> targets to build the other projects, but the files for those
>>>> projects don't get indexed so I lose out on features like code
>>>> insite. If I don't exclude the files, the indexer literrally give
>>>> me thousands of warnings ranging from #def warnings to preprocessor
>>>> inclusion warnings (#include).
>>>>
>>>> If I want to work on any of the other projects I have to open up
>>>> Visual Studio and work from there. Once VS is open, I can build all
>>>> of the projects and end up not returning to Eclipse.
>>>>
>>>> Thanks,
>>>>
>>>> David
>>>
>>>
>>>
>>>
|
|
|
| Re: Multiple projects on common src directory [message #156180 is a reply to message #153910] |
Thu, 13 October 2005 18:13 |
| Eclipse User |
|
|
|
Originally posted by: eclipse.dharty.com
I encountered the same problem with indexing, the indexer can find the
declarations, but not the definitions.
I have reverted to the "monolithic" project defined for one project with
multiple working sets to present the files needed by the different builds.
Thanks though, it would have been nice.
David
Keath Milligan wrote:
> Chip Chapin wrote:
>
>> It does work with CDT, but it's easy to miss:
>>
>> 1. Navigate to the Project | Properties | Project Paths | Source tab
>> as described by Doug.
>> 2. Click "Add Folder". A "Source Folder Selection" window pops up.
>> 3. Click "Create New Folder". A "New Folder" window pops up.
>> 4. Here's the part you probably missed: Click "Advanced". The New
>> Folder popup expands with an option to link to an [existing] folder in
>> the file system. Now you can refer to any folder you want.
>>
>> Chip
>
>
> I've been using this method in a similar scenario to what the original
> poster descibed, but I've had a lot of difficulty getting
> searching/indexing to work.
>
> It sure would be nice if there was a little more emphasis on standard
> make projects and integrating with existing, real-world codebases rather
> than simple text-book examples. There's a really big gap between "hello
> world" and a real project with thousands of files (in who-knows-what
> structure) and millions or lines of code, yet the latter is going to be
> a far more common challenge for people actually trying to deploy Eclipse.
|
|
|
Goto Forum:
Current Time: Wed Apr 24 23:37:00 GMT 2024
Powered by FUDForum. Page generated in 0.03436 seconds |
] 
Search
Help
Register
Login
Home
