Building BochsIA32Plugin

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
2 messages Options
Reply | Threaded
Open this post in threaded view
|

Building BochsIA32Plugin

Igor Stasenko
 
Hi, Eliot

you are the only one, who probably could answer this question

in
processors/IA32/bochs/conf.COG

i found following:

CPATH="/sw/include"
LDFLAGS="-L/sw/lib"

this looks like a dependency, which requred by Bochs code simulator to build..
what is it, and why it is needed?

as i can see, you using only following parts of it:
 - cpu, fpu and disasm

which actually a libs, and its quite easy to build them without too
much ad-hoc preparations.

So, i wonder, what if i just include all source files in these dirs as
a source files for boch's plugin lib,
and with proper compiler flags and defines, simply compile them into
single library
using plain CMakeLists.txt file,
without scary monstrosities like configure scripts (the only product
of it, which is really needed is generated config.h header).


Of course, i could instruct cmake to run configure script.. or
conf.COG .. whatever.
Just wanna be able to build this plugin without requiring user's attention.


--
Best regards,
Igor Stasenko AKA sig.
Reply | Threaded
Open this post in threaded view
|

Re: Building BochsIA32Plugin

Eliot Miranda-2
 
Hi Igor,

On Mon, Dec 27, 2010 at 3:09 AM, Igor Stasenko <[hidden email]> wrote:

Hi, Eliot

you are the only one, who probably could answer this question

in
processors/IA32/bochs/conf.COG

i found following:

CPATH="/sw/include"
LDFLAGS="-L/sw/lib"

this looks like a dependency, which requred by Bochs code simulator to build..
what is it, and why it is needed?

Good question.  It appears to be noise.  It is probably needed for the full pc-emulator build of Bochs, but not the subset that provides x86/x86-64 processor.  I've fixed this and will update soon.

best
Eliot
 

as i can see, you using only following parts of it:
 - cpu, fpu and disasm

which actually a libs, and its quite easy to build them without too
much ad-hoc preparations.

So, i wonder, what if i just include all source files in these dirs as
a source files for boch's plugin lib,
and with proper compiler flags and defines, simply compile them into
single library
using plain CMakeLists.txt file,
without scary monstrosities like configure scripts (the only product
of it, which is really needed is generated config.h header).


Of course, i could instruct cmake to run configure script.. or
conf.COG .. whatever.
Just wanna be able to build this plugin without requiring user's attention.


--
Best regards,
Igor Stasenko AKA sig.