[En-Nut-Discussion] Feature Request: Create Application Directory" for (q)nutconf

Thiago A. Corrêa thiago.correa at gmail.com
Wed Feb 15 20:38:12 CET 2012


I have been wondering for a while how we could have a "New Project
with Nut/OS" kind of wizard, like visual studio, into qnutconf and how
it would build you the basic makefiles. It's interesting to know how
ppl actually use Nut/OS in their environment.

In particular, I keep my nuts/os in c:\programming\ethernut and my
projects as c:\programming\comm5\firmware\<project>
Inside <project> I create a makefile that references the sample
makefiles like this:

include /programming/ethernut/nutapp/Makedefs

SRCS =  mysource.c
LIBS =  $(LIBDIR)/nutinit.o -lnutos -lnutarch -lnutdev -lnutcrt -lnutc -lnutgorp
OBJS =  $(SRCS:.c=.o)
TARG =  $(PROJ).hex

all: $(OBJS) $(TARG) $(ITARG) $(DTARG)

	$(CC) -I$(top_srcdir)/include -M main.c

include /programming/ethernut/nutapp/Makerules

It's simple and shouldn't be hard to generate, yet I don't think it's
simple enough for the beginner. I'm interested in opinions.

Kind Regards,
    Thiago A. Correa

On Sun, Feb 12, 2012 at 9:30 AM, Ulrich Prinz
<ulrich.prinz at googlemail.com> wrote:
> Hi!
> At first the separation of directory and makefile generation from
> creation of all examples would be very helpfull.
> To add an option that enables to export all libraries and headers and
> creates a set of working application makefiles is very fine.
> We often need to keep nut/os libraries synced with the application
> source code to be able to reproduce avery single software release.
> So if we could export the libraries and headers in parallel with the
> applications it would be very handy for checking them in to SVN or
> GIT.
> Ulrich
> Am 08.02.2012 15:52, schrieb Ole Reinhardt:
>> Hi Ulrich,
>>> But if you develop lots of your own projects you might not like to
>>> have all the examples installed.
>> Yes, I well know this problem. I personally prefer to have a
>> pre-compiled Nut/OS and to use just a few simple makefiles with my
>> application, not all this directory hirarchy.
>> Especialy when deploying Nut/OS as development environment for a board
>> your customers won't ever compile Nut/OS by their own but just use the
>> ready build libraries.
>> So what I would suggest is to add an "Install Nut/OS" which would build
>> the libraries, install it into a folder and add the necessary makefiles
>> (just the ones for your compiler setting)
>> As an example see
>> http://www.embedded-it.de/bsp-download/webserver_relais_demo.tar.gz
>> (folder Nut/OS)
>> I also modified the application standard makefiles to refer to the
>> pre-installed ones.
>> Another idea:
>> This install button could also copy the header files so that one would
>> not have to install the whole source tree too.
>> Bye,
>> Ole
> _______________________________________________
> http://lists.egnite.de/mailman/listinfo/en-nut-discussion

More information about the En-Nut-Discussion mailing list