On 9/7/12 11:09 PM, Matt Turner wrote:
On Fri, Sep 7, 2012 at 1:49 PM, Thomas Hellström wrote:
On 9/7/12 10:39 PM, Matt Turner wrote:
I'm converting the remaining static Makefile to automake, so xa and
xa-vmwgfx is on my todo list.
I'm very confused by the build though. It seems that the xa s
On Fri, Sep 7, 2012 at 9:49 PM, Thomas Hellström wrote:
> On 9/7/12 10:39 PM, Matt Turner wrote:
>>
>> I'm converting the remaining static Makefile to automake, so xa and
>> xa-vmwgfx is on my todo list.
>>
>> I'm very confused by the build though. It seems that the xa state
>> tracker is built an
On Fri, Sep 7, 2012 at 1:49 PM, Thomas Hellström wrote:
> On 9/7/12 10:39 PM, Matt Turner wrote:
>>
>> I'm converting the remaining static Makefile to automake, so xa and
>> xa-vmwgfx is on my todo list.
>>
>> I'm very confused by the build though. It seems that the xa state
>> tracker is built an
On 9/7/12 10:39 PM, Matt Turner wrote:
I'm converting the remaining static Makefile to automake, so xa and
xa-vmwgfx is on my todo list.
I'm very confused by the build though. It seems that the xa state
tracker is built and linked into a single .o file, which is then
statically linked into xa-vm
I'm converting the remaining static Makefile to automake, so xa and
xa-vmwgfx is on my todo list.
I'm very confused by the build though. It seems that the xa state
tracker is built and linked into a single .o file, which is then
statically linked into xa-vmwgfx. This is reasonably sensible, but
th
