[news.eclipse.tools.cdt] Re: How should I organize my project

["Ken Klose" <ken.klose@xxxxxxxxxxxxxxxx>]

Anders,

Thanks for taking the time to help me out! I guess my question wasn't 100% 
clear. I've already figured out that I'm going to deliver a static lib along 
with some (but not all header files).

My question is more on how to organize my project to facilitate this. Right 
now I've got the project folder full of cpp and h files. As it stands when 
delivery time comes I'll build the lib and manually copy it along with some 
of the header files onto a disk. This doesn't strike me as being the "right 
way". I'm hoping you (and/or someone else) can say "we organize our cpp 
files like xxx" and "the header files that are for our use only go here, and 
the header files we deliver go here". Etc.

Thanks,

Ken

"Anders Hansson" <anders@xxxxxxx> wrote in message 
news:f0lvhm$7a6$1@xxxxxxxxxxxxxxxxxxxx
> Ken Klose wrote:
>> I'm a C++ n00b using CDT Callisto to develop a access library to an
>> existing
>> product.  Right now I've the default CDT project layout - namely a bunch
>> of
>> .h files and .cpp file in the root directory of the project.  How should 
>> I
>> organize this better.
>>
>> Also is there a way to hide parts of library from the eventual users.
>> There is plenty of implentation details that I don't want to confuse 
>> users
>> with. I want them to see the API they need, not the classes I'm using
>> under the covers to make it all work.
>
> How about making your access library - a library. (Build it as a static or
> shared library). You only need to provide the appropriate header files
> (i.e. the API) to your library users.
>
> Your users add your static/shared library to their linker settings and
> include your header file for the library.
>
> /Anders