Re: [cdt-dev] Build Update

[Mike Jackson <mike.jackson@xxxxxxxxxxxxxx>]

And just to follow up, that person has no written a "tutorial" about
setting up his ITK project with Eclipse.

On 3/11/10 10:01 AM, Antonin Perrot-Audet wrote:

    I finished configuring the project yesterday, and wrote a small
"how to configure Eclipse with a CMake-ITK project"

    Any feedback would be appreciated.

Already one error detected/corrected : new version :
http://fex.insa-lyon.fr/get?k=hH9rWzEll3ggNtwgWgX

I will wait until the end of the day and post an updated version
according to comments. I guess there will be english mistakes !
regards


-- 
Antonin Perrot-Audet
Electrical Engineering&  Computer Sciences, INSA Lyon
M2 GEGP Signal&  Image Processing, INSA Lyon, UCBL, Centrale Lyon

-----------------

Again, Might be enlightening to read what a novice user goes through.
_________________________________________________________
Mike Jackson                  mike.jackson@xxxxxxxxxxxxxx

On Wed, Mar 10, 2010 at 9:26 AM, Michael Jackson
<mike.jackson@xxxxxxxxxxxxxx> wrote:
>   Just FYI
> <http://www.itk.org/pipermail/insight-users/2010-March/035675.html> is the
> start of an email thread with a new CDT user coming from Xcode and trying to
> get everything setup correctly. Might be enlightening to see what someone is
> going through.
>
> ___________________________________________________________
> Mike Jackson                      www.bluequartz.net
>
> On Mar 3, 2010, at 11:09 AM, Doug Schaefer wrote:
>
>> On Wed, Mar 3, 2010 at 8:56 AM, Michael Jackson
>> <mike.jackson@xxxxxxxxxxxxxx> wrote:
>> On 3/2/2010 10:48 PM, Doug Schaefer wrote:
>> BTW, I find CMake's CDT project generator weird. We've always claimed the
>> .cproject format and contents to be internal interfaces which could change
>> at any time. And you have a chicken/egg situation. If you are using the CDT
>> with your project, you'll already have these files created. At any rate, I'd
>> prefer to use CMake as a Makefile generator only.
>> Probably using CMake in that capacity is the best way to implement it.
>> That way I do not have to actually have CDT running if I want to do a quick
>> build from the command line (like if I was SSH'ed into my OS X box).
>>
>>  Typically one would use CMake to generate the IDE project files. Then
>> "Double click" the project file in order to Launch the IDE and load the
>> project. CDT does not work this way at all and you end up with like you
>> stated. Do I launch CDT first then do CMake or CMake then Eclipse? I think
>> the general consensus is that when starting from a clean project directory
>> (which MUST be located in the workspace), you would create the build
>> directory, use CMake to generate the CDT files, switch to CDT, then use
>> "Import Project" to import the project into your workspace. Not better, not
>> worse, just different. QtCreator is not much better. It leaves project files
>> sprinkled all throughout my source directories which becomes messy when
>> something like CVS/SVN/Git is used.
>>
>>
>> That's a great point and another major issue, especially for people coming
>> from Visual Studio, and something we've talked about in the past. We really
>> need a project system that isn't forced to map to the file system, in
>> particular make a .project file work like other IDEs and list the resources.
>> Then the CMake strategy would make sense. There's some interesting work
>> going on in e4 right now by the folk at SAP about enabling RESTful resources
>> that might be applicable here.
>> _______________________________________________
>> cdt-dev mailing list
>> cdt-dev@xxxxxxxxxxx
>> https://dev.eclipse.org/mailman/listinfo/cdt-dev
>
>