Friday, February 25, 2005

yeah i got it....

the solution to pyuno error, it is because of linking with cc and cxx. I found that OO use linker as ${CC}, on the bugs and issue tracker i found a issue numbered 37731 related to same problem and came to know that this pyuno problem can be rectified by changing link to ${CXX} AND this change in linker to cxx can be achieved by the following patch:

Index: config_office/set_soenv.in
===================================================================
RCS file: /cvs/tools/config_office/set_soenv.in,v
retrieving revision 1.31
diff -u -r1.31 set_soenv.in
--- config_office/set_soenv.in 5 Jan 2005 12:10:00 -0000 1.31
+++ config_office/set_soenv.in 9 Jan 2005 18:51:24 -0000
@@ -1684,9 +1684,6 @@
ToFile( "CC", $CC, "e" );
ToFile( "CXX", $CXX, "e" );
ToFile( "USE_SYSTEM_STL", "@USE_SYSTEM_STL@", "e" );
-if ( $COM ne "MSC" ) {
- ToFile( "LINK", $CC, "e" );
-}
ToFile( "ENABLE_SYMBOLS", "@ENABLE_SYMBOLS@", "e" );
ToFile( "ENABLE_CRASHDUMP", "@ENABLE_CRASHDUMP@", "e" );
ToFile( "ENABLE_CUPS", "@ENABLE_CUPS@", "e" );

But one has to build the complete source again after applying this patch this is what i have done and rectified the error.

No comments: