Re: [Anjuta-list] Using custom makefile instead of automake

[Timothee Besset <ttimo idsoftware com>]

When you import an existing project, anjuta will consider that it is not
auto* managed and won't attempt to generate/update makefiles for you. The
easiest step then is to create a 'tool' for compilation:

Settings > Tools Editor > new

And put this command in the build menu.

TTimo

On Mon, 10 Mar 2003 09:06:06 +0100
Gunnarsson Samúel Jón <F32390 DANFOSS com> wrote:

> Hi everyone
> 
> First and foremost i must say that i'm a total newbie in using Anjuta
> development 
> enviorment and programming in linux for that matter. I currently working on
> a project
> at www.danfoss.com wich involves porting software platform they use to the
> linux 
> platform and later to embedded linux platform. 
> 
> My problem is as follows.
> 
> I have imported the project that i'm working on into anjuta. But the problem
> is that this
> project has a Makefile of its own that I would like to use. After browsing
> through various 
> configuration option leads me to the conclusion that there maybe no
> possibility to use 
> my own Makefile.
> 
> So my question is.
> 
> 1. Is it possible to use my own custom makefile instead of autogenerated one
> that will give
> errors in my case.
> 
> 2. Would it be possible to hack the project file so that it will point to my
> makefile wich
> stores all of my cflags, sources and so forth.
> 
> Regards 
> Samuel Jon Gunnarsson
> 
> 
> 
> 
> 
> -------------------------------------------------------
> This SF.net email is sponsored by: Etnus, makers of TotalView, The debugger 
> for complex code. Debugging C/C++ programs can leave you feeling lost and 
> disoriented. TotalView can help you find your way. Available on major UNIX 
> and Linux platforms. Try it free. www.etnus.com
> _______________________________________________
> Anjuta-list mailing list
> Anjuta-list lists sourceforge net
> https://lists.sourceforge.net/lists/listinfo/anjuta-list
>