Skip to main content

mustang source - possible to build only native parts?

3 replies [Last post]
tb
Offline
Joined: 2005-04-05

"make scsl" will vuild all stuff. is there an option or some flags, to build only the native part of the jre ?

Thomas

Reply viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.
bino_george
Offline
Joined: 2003-06-16

> "make scsl" will vuild all stuff. is there an option
> or some flags, to build only the native part of the
> jre ?
>
> Thomas

I dont think you can do this for a fresh build. The reason
being that you need the JNI header files generated from the
class files using javah. But it may be possible to do this
once you have built the whole thing. I will check with
Kelly and Vijay.

Regards,
Bino.

kellyohair
Offline
Joined: 2004-09-03

I will file an RFE to try and accomplish this but haven't had time to make the necessary changes to the j2se makefiles, and more importantly verify the theory works.

The idea is to import the pre-built libraries (*.so's and DLL's) just like the it does now for Hotspot VM. Using the location JDK_IMPORT_PATH (or your own ALT_JDK_IMPORT_PATH setting) as the source of the built libraries. It would be important that this JDK binary match what you are building and also that you aren't changing any of the native interfaces. If this worked, a C/C++ compiler might not even be necessary for anyone just making changes to Java source files. But you would need a matching built JDK 6.0 binary tree.

See RFE http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6288957.

-kto

kellyohair
Offline
Joined: 2004-09-03

I must confess to getting this backwards, sorry.

The question was about building just the native parts of the JDK. Bino was right, often we need the class files to run through javah to get the include files in order to compile the native code. So we have some dependency issues here. My previous post was for 'not building the native parts'. :^(