From: Marcel Holtmann <marcel@holtmann.org>
To: Keith Pemberton <kbpember@cox.net>
Cc: BlueZ Mailing List <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] Development IDE sugguestion?
Date: Sun, 28 Mar 2004 10:33:31 +0200 [thread overview]
Message-ID: <1080462811.2281.94.camel@pegasus> (raw)
In-Reply-To: <1080460219.3641.4.camel@linuxcomp.gatep5.net>
Hi Keith,
> I am trying to get started with developing kernel drivers, but I need
> some initial assistance. I was looking for a good IDE that I can use
> with good code completion capabilities. Anyone got any suggestions?
> What are you guys using for developing the Bluez stack? I have tried
> Kdevelop and Anjuta but I can seem to get started with new projects
> under these. The initial configure scripts always fail and when ever I
> add a new include directive I get a bunch of error/warning messages. I
> know that I have so much to learn about this new world, but I would
> appreciate your help and advice in getting started. Thanks in advance!
I am using anjuta as editor, but I am writing the autoconf/automake
files by myself.
Regards
Marcel
-------------------------------------------------------
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
prev parent reply other threads:[~2004-03-28 8:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-28 7:50 [Bluez-devel] Development IDE sugguestion? Keith Pemberton
2004-03-28 8:33 ` Marcel Holtmann [this message]
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=1080462811.2281.94.camel@pegasus \
--to=marcel@holtmann.org \
--cc=bluez-devel@lists.sourceforge.net \
--cc=kbpember@cox.net \
/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 NNTP newsgroup(s).