[Olsr-dev] eclipse project files

Hans-Christoph Steiner (spam-protected)
Wed May 9 20:40:59 CEST 2012



On 05/09/2012 05:15 AM, Ferry Huberts wrote:
> 
> 
> On 09-05-12 11:08, Henning Rogge wrote:
>> On 05/09/2012 10:09 AM, Ferry Huberts wrote:
>>> Not sure what you mean.
>>> As you said yourself, olsrd uses an external makefile and I've
>>> configured eclipse to use that same makefile.
>>
>> I use different build targets in my CDT settings to work on Linux and
>> Win32 compilation. Which means my .cproject file will be different and
>> my different copy will be committed to the repository when I push a
>> change.
>>
> 
> ok.
> we can solve that easily with separate build configurations in eclipse.
> I will push my eclipse config into a branch so you can look at it and
> add a mingw build configuration (if you like).
> 
>>>> If we put the files in, generating your own configuration becomes more
>>>> difficult because your changes might be accidentally pushed back into
>>>> the main repository.
>>>>
> 
> that's a bit the point ;-)
> 
>>>> Maybe we could put two example files (project/cproject) into the files
>>>> folder?
>>>>
>>>
>>> I think this adds no value. My point is that it would be awesome to
>>> clone and then import in eclipse and be able to start work right away
>>
>> We could add an extra line into the default makefile that copies both
>> files to the main directory if they are not present. This way you have a
>> quick way to start with eclipse, but you are not always in danger to
>> overwrite the default project settings with your own.
>>
> 
> I would not prefer that because that would make a change in the project
> configuration difficult to commit

I agree that the files should only be included in their standard
location, its not really worth doing it in files/, I think it'll just
add confusion.  If its possible to include all the needed build
configurations, it would be nice to have these files in place.

.hc




More information about the Olsr-dev mailing list