qemu-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Qemu-devel] Re: [PATCH 3/3] Workaround --whole-archive on Solaris


From: Avi Kivity
Subject: [Qemu-devel] Re: [PATCH 3/3] Workaround --whole-archive on Solaris
Date: Sun, 13 Dec 2009 12:21:16 +0200
User-agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.1.5) Gecko/20091203 Fedora/3.0-3.13.rc2.fc12 Thunderbird/3.0

On 12/13/2009 01:07 AM, Andreas Färber wrote:

Certainly I would prefer having one shared linking mechanism.

The three separate Makefiles (Makefile, Makefile.hw, Makefile.target) that govern which objects are to be compiled pose the problem. In the end, we need some mechanism to get the right set of objects into Makefile.target. Previous attempts were
(i) writing object file paths to a file (me not satisfied), or
(ii) printing them from within make (Avi objected), and now
(iii) extracting them from archives (Juan objected for Linux).

Out of the three above, I prefer (ii) despite my objection.


Juan, being our Makefile inventor, what about
(iv) moving the assembling of some of the obj-y variables to a shared file included by all three Makefiles? Would that work? If we had, e.g., common-obj-y and libhw{32,64}-obj-y accessible in Makefile.target, we could use them for both dependency modelling and linking.

But out of the four, I prefer this.

In fact, why not have one large makefile, with different targets called for different subdirectories?

--
error compiling committee.c: too many arguments to function





reply via email to

[Prev in Thread] Current Thread [Next in Thread]