setting up include path for muli-lib project

[Andrew Skiba]

Hello all!   
I asked about subj few days ago and got a nice answer here. To remind, it was 
about right way to build an app with few shared libs. Now, I came to what  
shared libs were built for - sharing the shared libs :-).  
Don't blame me for using examples with VC, but this is the way I worked for  
last 7 years :-(((, they are used only for illustration. So, I'm used to set up 
the projects' folders like the following:  
  
projects/  
	DebugBin/  
	ReleaseBin/  
	app1/  
	app2/  
	lib1/  
	lib2/  
  
The idea is that the shared libraries are on the same level with the  
applications. It really makes sense - the libraries don't really belong to any 
of them, they are _shared_. In VC I set up each project to put the final .exe's 
and .dll's in ../DebugBin or ../ReleaseBin, depending on the configuration.  
  
In KDevelop I have to put the libraries' directories under the applications'  
ones, so the tree has to look like 
  
projects/  
	app1/  
		lib1/  
		lib2/  
	app2/  
		lib1/  
		lib2/  
  
It's obvious that having two (well, it will be more than two, actually) full  
copies of lib directories is impractical. I tried to put the libraries' dirs to 
the projects/, and create symbolic links to them in the app1 and app2, but 
could not find the way to build even a single application.  
  
projects/  
	lib1/  
	lib2/  
	app1/  
		link to ../lib1/  
		link to ../lib2/  
	app2/  
		link to ../lib1/  
		link to ../lib2/  
  
It would be interesting to hear from people that manage multiple projects with 
shared libraries, how do they set the whole thing up? 
  
Thanks for any ideas.  
Andrew Skiba.  
  


-
to unsubscribe from this list send an email to kdevelop-request at kdevelop.org with the following body:
unsubscribe ╩your-email-address╚