public inbox for crossgcc@sourceware.org
 help / color / mirror / Atom feed
From: mike@penbex.com.tw (mike)
To: <crossgcc@sources.redhat.com>
Subject: Fw: the GTK AP for cross compiling
Date: Sun, 01 Apr 2001 00:00:00 -0000	[thread overview]
Message-ID: <003a01c07ac4$4d092ec0$9e0150c0@penbex.com.tw> (raw)
Message-ID: <20010401000000.BupaD1wAyCg6yyeRCNnrt-1JU-qWGOtgSvPNMzbSNZA@z> (raw)

You got port gtk to arm first if You wanna run gxhost on your target board.
That means you have to rewrite gdk's display code just like gtk-win32 did.
To produce the right Makefile directly can be done using 'configure' script,
but I'm not sure it will works under cross-compile on arm.
I still recommand drop you mail to
gtk-devel-list@gnome.org

BTW. gtk-win32 in
http://user.sgic.fi/~tml/gimp/win32/

> ----- Original Message -----
> From: chendyg
> To: crossgcc@sources.redhat.com
> Sent: Wednesday, January 10, 2001 12:13 PM
> Subject: the GTK AP for cross compiling
>
>
> Hello;
>   Now I download one  tar-ball of AP:gxhost.
>   when I untar it and make it for pc. ALl s right.
>   But I should do the cross compiling for arm.
>   who can tell me how to do for these config files I mean you can tell me
> one easy way.
>    Now I know to change the Makefile. Could you tell me the way which can
> produce the right Makefile directly for all of the source files in
different
> directory.
> joshua chen
>


------
Want more information?  See the CrossGCC FAQ, http://www.objsw.com/CrossGCC/
Want to unsubscribe? Send a note to crossgcc-unsubscribe@sourceware.cygnus.com

             reply	other threads:[~2001-04-01  0:00 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-01-09 21:15 mike [this message]
2001-04-01  0:00 ` mike

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='003a01c07ac4$4d092ec0$9e0150c0@penbex.com.tw' \
    --to=mike@penbex.com.tw \
    --cc=crossgcc@sources.redhat.com \
    /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).