From: "Timothy M. Shead" <tshead@k-3d.com>
To: leonp@plris.com
Cc: sourcenav@sources.redhat.com
Subject: Re: Source navigator roadmap, features list, etc.?
Date: Wed, 04 Oct 2000 02:42:00 -0000 [thread overview]
Message-ID: <39DAFB81.9010107@k-3d.com> (raw)
In-Reply-To: <4.3.2.7.0.20001004105753.00b142d8@plris.com>
leonp@plris.com wrote:
> At 16:02 03/10/2000 -0700, Mo DeJong wrote:
>
>> On Wed, 27 Sep 2000, William Gacquer wrote:
>> > 9/ a autoconf/automake project creation as in kdevelop
>>
>> This one is hard to do in a general way, but we could do
>> something like writing a configure.in for the user in the
>> same way that we write a Makefile.
>
> As far as I was able to understand the SN was designed for use also
> (mainly?) in Embedded Programming, where you need to have a little bit
> simpler and closer approach to a lot of build process parameters.
> Absence of this simple approach in kdevelop (which is very good IDE!)
> was the main reason that I left my attempts to sufficiently and
> comfortably integrate the embedded projects into it, while one of the
> main difficulties was this autoconf/automake stuff. I shall be very
> disappointed if this issue will be introduced also in SN, which is my
> only IDE today.
Remember that you can always use external commands to build any way you
like - I prefer to use my own makefiles, so my "Build Command" is set to
"make", "Directory" to my top-level project directory, and "Build
Targets" to "<External Makefile>". This shouldn't make anyone nervous :)
Timothy M. Shead
next prev parent reply other threads:[~2000-10-04 2:42 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-10-04 0:53 leonp
2000-10-04 2:42 ` Timothy M. Shead [this message]
-- strict thread matches above, loose matches on Subject: below --
2000-10-05 1:16 William Gacquer
2000-10-05 0:52 dave.banham
2000-09-29 0:26 dave.banham
2000-09-29 11:32 ` Syd Polk
2000-09-28 0:23 dave.banham
2000-09-28 13:25 ` Syd Polk
2000-09-28 17:28 ` Ben Elliston
2000-09-29 6:06 ` Bruce Stephens
[not found] <William>
[not found] ` <Gacquer's>
[not found] ` <message>
[not found] ` <of>
[not found] ` <"Wed,>
[not found] ` <27>
[not found] ` <Sep>
[not found] ` <2000>
[not found] ` <10:12:49>
[not found] ` <+0200>
2000-09-27 1:12 ` William Gacquer
2000-09-27 22:16 ` Bruce Stephens
2000-09-28 9:15 ` Berek
2000-09-28 13:26 ` Syd Polk
2000-09-28 13:22 ` Syd Polk
2000-10-03 16:02 ` Mo DeJong
2000-10-04 10:25 ` Syd Polk
2000-09-25 22:04 Timothee Besset
2000-09-26 9:23 ` Syd Polk
2000-09-26 10:30 ` Berek
2000-09-26 10:37 ` Syd Polk
2000-09-27 21:41 ` Ben Elliston
2000-10-03 9:44 ` Mo DeJong
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=39DAFB81.9010107@k-3d.com \
--to=tshead@k-3d.com \
--cc=leonp@plris.com \
--cc=sourcenav@sources.redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).