From: Gilles Chanteperdrix <gilles.chanteperdrix@xenomai.org>
To: Franz Engel <franz_lambert_engel@domain.hid>
Cc: xenomai@xenomai.org
Subject: Re: [Xenomai-help] valgrind and modprobe xeno_posix
Date: Thu, 17 Feb 2011 22:13:22 +0100 [thread overview]
Message-ID: <4D5D8F72.4010904@domain.hid> (raw)
In-Reply-To: <592273.9623.qm@domain.hid>
> Spam detection software, running on the system "xenomai.org", has
> identified this incoming email as possible spam. (...)
Please avoid HTML messages.
Franz Engel wrote:
> O.k. This is a quite helpfull information. I tried to make dynamic
> librarys and glue them with QT to my whole project. But, how I say,
> I'm a newbie with makefiles. I tried to trim the satch-example. This
> is my makefile: APPLICATION = demoLib XENO?=/usr/xenomai
> XENOCONFIG=$(shell PATH=$(XENO):$(XENO)/bin:$(PATH) which xeno-config
> 2>/dev/null) CC=$(shell $(XENOCONFIG) --cc) CFLAGS=$(shell
> $(XENOCONFIG) --posix-cflags) $(APP_CFLAGS) LDFLAGS=$(shell
> $(XENOCONFIG) --posix-ldflags) $(APP_LDFLAGS) LDFLAGS+=Xlinker -rpath
> -Xlinker $(shell $(XENOCONFIG) --libdir)
>
> all:: $(APPLICATIONS) clean:: $(RM) $(APPLICATIONS) *.o
>
> The demoLib works fine, but of course, it is no lib. What I have to
> change to make a lib? Did I understand it right that the xeno-config
> is a skript that gives support to get the *FLAGS easier? But where is
> the compiling comand?
Well, it is a bit off-topic, what you are asking is how to compile
libraries for Linux on your target. See for instance:
http://www.yolinux.com/TUTORIALS/LibraryArchives-StaticAndDynamic.html
--
Gilles.
prev parent reply other threads:[~2011-02-17 21:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-17 9:45 [Xenomai-help] valgrind and modprobe xeno_posix Franz Engel
2011-02-17 10:07 ` Gilles Chanteperdrix
2011-02-17 13:32 ` Franz Engel
2011-02-17 21:13 ` Gilles Chanteperdrix [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=4D5D8F72.4010904@domain.hid \
--to=gilles.chanteperdrix@xenomai.org \
--cc=franz_lambert_engel@domain.hid \
--cc=xenomai@xenomai.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.