customizing projects

[Markus Wagner]

Hi Ralf,

I didn't use automake/autoconf in the project before. Generating a kdevelop 
project in the directory makes a project, which just calls the old Makefile.
So I'd really like to use an empty C project generated by kdevelop and put in 
my sources step by step. But the directory naming confuses me.

I tried to use the template in 
/opt/kde2/share/apps/kdevelop/templates/c.tar.gz. I renamed "skel" to "src" 
and "|NAMELITTLE|" in some files. Then, configure and auto* run fine, but it 
still doesn't compile ("nothing to be done"...).

Markus

On Monday 10 September 2001 09:11, you wrote:
> On Montag, 10. September 2001 05:39, you wrote:
>
> Hi Marcus,
>
> in the best case, you should use "Project" -> "Generate Projectfile" on
> your old project. That means, you still have to write your Makefile.am's by
> yourself as KDevelop doesn't have an AI right now to determine your project
> structure. With 3.0 this will work (does already but currently not ready
> for production use).
>
> Ralf
>
> > Hi,
> >
> > I would like to port an existing project to KDevelop, but there is one
> > thing I have customization problems with.
> >
> > KDevelop always makes a subdirectory under the project
> > directory, which has the same name as the project. So I always have
> > something like "myProject/myProject". I would like to name this
> > subdirectory "myProject/src".
> >
> > Well, I changed it, changed Makefile.am (subdirs=) and all occurrences of
> > "myProject/" in the project file, but there are still problems, and
> > KDevelop will recreate "myProject/myProject".
> >
> > Are there any hints for fixing this? I would really like to work with
> > KDevelop.
> >

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