Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Bernhard Fischer <rep.nop@aon.at>
To: buildroot@busybox.net
Subject: [Buildroot] [patch] qtopia4
Date: Mon, 11 Dec 2006 23:27:08 +0100	[thread overview]
Message-ID: <20061211222708.GE4442@aon.at> (raw)
In-Reply-To: <20061211215648.GA15000@zelow.no>

On Mon, Dec 11, 2006 at 10:56:48PM +0100, Thomas Lundquist wrote:
>On Mon, Dec 11, 2006 at 02:43:47PM +0100, Bernhard Fischer wrote:

>> >+	$(SED) 's/-O2/-Os/;' $(QTOPIA4_TARGET_DIR)/mkspecs/qws/linux-$(BR2_PACKAGE_QTOPIA4_EMB_PLATFORM)-g++/qmake.conf
>> 
>> shouldn't this rather be
>> s/-O2/-Os $(TARGET_CFLAGS)/
>
>then it could be 
>s/-O2/$(TARGET_CFLAGS)/
>
>since -Os should be included.

Yes.
>
>Something tells me that I shouldn't do that here. Don't ask me why, I
>spent quite alot of time getting qtopia to compile at all.

Trouble is that some arches may need some fancy flags to generate proper
code, users may want to globally set some additional flags that should
be used for all packages that are built. Please verify if passing the
correct TARGET_CFLAGS down to qtopia works as expected thus area lso
used in qtopia.
>
>> Also, all trailing command separators (i.e. ';') in sed are superfluous.
>
>It's a habit. Any real reason we should make it a requirement not to
>have it or is it just for looks?

Well, it's bloat :) Habit of mine to omit them if they are not needed.
>
>> >+	cp $(QTOPIA4_QCONFIG_FILE) \
>> >+	 	$(QTOPIA4_TARGET_DIR)/$(QTOPIA4_QCONFIG_FILE_LOCATION)
>> >+	(cd $(QTOPIA4_TARGET_DIR); rm -rf config.cache; \
>> >+		PATH=$(TARGET_PATH) \
>> >+		CFLAGS="$(TARGET_CFLAGS)" \
>> >+		CXXFLAGS="$(TARGET_CXXFLAGS)" \
>> 
>> Sounds like this is will break for anybody that doesn't have a plain
>> "gcc" nor "g++" binary. Honor the user's HOSTCC and HOSTCXX vars,
>> please.

Of course ment CC and CXX and not the host compilers, sorry.
>
>If Troll/qtopia would, I would.
>(No, they don't seem to honour CC nor CXX)

Can't be.. Otherwise you'd build qtopia for the host and not for the
target. Please double check (could be that configure stores them for
you).


>I'll send you a new patch with or without ;.
>(and if you really don't want them I guess I have to remove them from
>other packages I've planned to submit.)

Please do. It just wastes space and memory.
Thanks,

  reply	other threads:[~2006-12-11 22:27 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-12-11  9:33 [Buildroot] [patch] qtopia4 Thomas Lundquist
2006-12-11 10:24 ` Bernhard Fischer
2006-12-11 10:48   ` Ulf Samuelsson
2006-12-11 12:00   ` Thomas Lundquist
2006-12-11 13:43     ` Bernhard Fischer
2006-12-11 21:56       ` Thomas Lundquist
2006-12-11 22:27         ` Bernhard Fischer [this message]
2006-12-12  8:38           ` Thomas Lundquist
2006-12-12 10:05             ` Allan Clark
2006-12-12 10:21               ` Bernhard Fischer
2006-12-12 15:43               ` Thomas Lundquist
2006-12-13 20:09             ` Bernhard Fischer

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=20061211222708.GE4442@aon.at \
    --to=rep.nop@aon.at \
    --cc=buildroot@busybox.net \
    /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