public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: David Fernandez <david.fernandez.work@googlemail.com>
To: ecos-discuss@ecos.sourceware.org
Subject: [ECOS] Re: configtool for linux building problems.
Date: Thu, 21 Jun 2012 22:57:00 -0000	[thread overview]
Message-ID: <4FE3A6C0.10706@googlemail.com> (raw)
In-Reply-To: <4FE22BA0.6040705@googlemail.com>

As people is quite busy these days, I eventually find the answer myself:

The best ecos help page for configtool and host tools in general is
http://www.ecoscentric.com/devzone/configtool.shtml, the README.txt in
ecos/host/tools/configtool/standalone/wxwin gives a make recipe that is
less flexible then the one indicated in the web page.

1.- The link to wxGTK-2.8.8 sources in the above, or any other
wxGTK-2.8.x sources are ok, but require a few tricks. After configuring,
building, and installing, as indicated in the eCosCentric web page for
configtool, while in the wxGTK build folder (not the sources one) do:
    cd contrib/src/gizmos
    make
    sudo make install
This should get the gizmos library and headers installed, which do not
seem to install by default.

2.- Edit the makefile.gnu in ecos/host/tools/configtool/standalone, and
add to the line EXTRALDFLAGS, at the end, after leaving a space, -lX11

3.- Build configtool as indicated in
http://www.ecoscentric.com/devzone/configtool.shtml
    sudo make -f
<path-to>/ecos/host/tools/configtool/standalone/wxwin/makefile.gnu \
                        install WXDIR=<wxgtk-install-prefix>
ECOSSRCDIR=<path-to>/ecos/host \
                        INSTALLDIR=<configtool-install-prefix>
The makefile.gnu has the full possible options, but if your tcl is
properly installed, only the ones shown above will be necessary.

N.B. wxGTK-2.9 has either integrated gizmos into normal wxGTK source
folders, or moved part of it to "wxCode" (perhaps an additional package
to configure --with-wxcode, but not sure).

Hopefully I'll be able to find this the next time... Although it would
be good to update the ecos.sourceware.org pages with this info, perhaps
the eCosCentric ones too.

By the way, if John Dallaway, or any other maintainer for configtool
could confirm its maintenance status, and if what I've put above is the
best way to solve the configtool build problems, that would be great.

Cheers

-- 
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss

  reply	other threads:[~2012-06-21 22:57 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-20 16:21 [ECOS] " David Fernandez
2012-06-20 19:59 ` [ECOS] " David Fernandez
2012-06-21 22:57   ` David Fernandez [this message]
2012-06-22  7:54     ` John Dallaway
2012-06-22 18:26       ` David Fernandez
2012-06-22  9:18     ` Alex Schuilenburg
     [not found] <4FE4C8BC.80600@dallaway.org.uk>
2012-06-22 19:42 ` John Dallaway
2013-07-11 10:24   ` scas
2013-07-11 12:54     ` John Dallaway
2013-07-11 13:32       ` scas
2013-07-13 19:28         ` scas

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=4FE3A6C0.10706@googlemail.com \
    --to=david.fernandez.work@googlemail.com \
    --cc=ecos-discuss@ecos.sourceware.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 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).