-
Bug
-
Resolution: Fixed
-
P3
-
6
-
b46
-
generic
-
generic
Sometimes the .o/.obj files export different interfaces when built with debug/fastdebug vs.
product builds. The .o/.obj files should be kept separate.
Mixing up of the different .o files can cause failures and surprises.
The location of the DLL or .so file can remain the same, all variants delivering it into
the same place. (This may require some experimentation due to makefile timestamp comparisons of
the DLL or .so with the .o files, a copy of the DLL or .so may need to remain in the same area
as the .o files.)
It should be easy to just re-build one component with fastdebug/debug without having to
don a 'gnumake clean' all the time.
###@###.### 2005-05-31 17:48:31 GMT
product builds. The .o/.obj files should be kept separate.
Mixing up of the different .o files can cause failures and surprises.
The location of the DLL or .so file can remain the same, all variants delivering it into
the same place. (This may require some experimentation due to makefile timestamp comparisons of
the DLL or .so with the .o files, a copy of the DLL or .so may need to remain in the same area
as the .o files.)
It should be easy to just re-build one component with fastdebug/debug without having to
don a 'gnumake clean' all the time.
###@###.### 2005-05-31 17:48:31 GMT
- relates to
-
JDK-6288957 Allow for IMPORT of any DLL/.so from JDK_IMPORT_PATH instead of building it
-
- Resolved
-