From: Mark Wielaard <mark@klomp.org>
To: Thomas Girard <thomas.g.girard@free.fr>
Cc: Frysk Hackers <frysk@sourceware.org>
Subject: Re: Questions about build web documentation
Date: Thu, 09 Aug 2007 10:24:00 -0000 [thread overview]
Message-ID: <1186655070.3747.12.camel@dijkstra.wildebeest.org> (raw)
In-Reply-To: <1186647756.3865.14.camel@micmac>
[-- Attachment #1: Type: text/plain, Size: 1170 bytes --]
Hi Thomas,
On Thu, 2007-08-09 at 10:22 +0200, Thomas Girard wrote:
> I have started modifying the htdocs/build/index.html file to add
> sections for Debian (and Ubuntu Gutsy Gibbon).
Thanks, great.
> There's something I don't understand about this page: according to it
> jdom, junit and junit packages are required to build frysk. But they're
> not because they are available from frysk-imports. Am I missing
> something? (Besides, using system versions of these libraries - as we do
> for Debian frysk package - require tweaking some autotools files.)
This might be slightly outdated then. antlr and jdom jars are used from
the system if found (see frysk-imports/configure.ac), for junit,
cdtparser, jline and getopt, we do include the upstream sources (see the
frysk-import/ subdirs) and compile those to jar files. Then in
frysk-imports/bootstrap.sh (FILE_LIST) we feed those, and the detected
antlr and jdom jars, to common/Makefile.gen.sh that creates a
frysk-imports/Makefile.gen, that is included in the
frysk-imports/Makefile.am so that we finally generate native shared
libraries from them, which we link against.
Cheers,
Mark
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2007-08-09 10:24 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-09 8:27 Thomas Girard
2007-08-09 10:24 ` Mark Wielaard [this message]
2007-08-12 20:38 ` Thomas Girard
2007-08-20 21:28 ` Phil Muldoon
2007-08-20 22:02 ` Thomas Girard
2007-08-21 7:31 ` Mark Wielaard
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=1186655070.3747.12.camel@dijkstra.wildebeest.org \
--to=mark@klomp.org \
--cc=frysk@sourceware.org \
--cc=thomas.g.girard@free.fr \
/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).