Re: [dev] Built and now what ?
Jim Watson wrote: Enno, the original question (I may have mis-read) I thought was "after building, how can it be run?" Now i see it is more about solver, about which I have no experience. I will make some very brief comments below, and reply more fully later today. maybe someone else will comment? With solver still have to build but that got slowly hidden in my messages. Solver does still not do much solving for me but ... I think the best thing would be to download the released installation that matches your solver version and use that one to drop in your changes. jim I read the documentation for the umpteenth time and noticed that dmake does a build and a deliver. I could do porting/sal> build debug=true so now I did porting/sal> deliver As documented that transfers all files built (any a few more) to the solver tree. Invoking the 'soffice' script in solver tree still does not work but followed your idea and replaced link for libuno_sal.so.3 in opt/openoffice.org2.0/program to point to new library in solver. That works so now I can start the real quest. Still would like to know how to run 'properly' from solver but less urgent. Thanks for help. Enno On 07/11/2006, at 2:56 AM, Enno Fennema wrote: 7) Make an installation set cd $SRCROOT; source xxxEnv.Set; cd installation/instset_oo build -u What version is it? I have $SRCROOT/instsetoo_native An installation set is a file or set of files describing all files needed to make an installation package for a particular product/ platform/ language (?) (Some kind of concatenation of .scp files ?) It is the final product ready to be installed by the user. Step 7 maakes it it. 8) Make a package based on the installation set Don't know yet. Now you are the user - just install it somewhere 9) Get appropriate install script from an openoffice.org/developer mirror (Necessary once you have an .rpm package?) Sufficient, but not necessary if you know how. 10)Install the package in some directory eg. ~/ootrial running rpm -i --prefix=/home/me/ootrial Definitively the core package but maybe others? Everything except desktop integration (i think) 11) Run ~/ootrial//soffice Find problem and back to 6) or live happy ever after. ~/ootrial/program/soffice In 7) things go wrong for me. After some preliminaries error: find: /loc/prog32/oomodules/default_images/res/commandimagelist: No such file or directory Help! anyone? IMHO you need checkout default_images module. It is referenced directly from instsetoo_native so the solver is not complete (bug or feature?) But see my top comment - get the ready-made installation If 11) is the last step I am over halfway. 99% - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[dev] instsetoo_native build failure
My build instsetoo_native fails in packimages when looking for *.png files in $SRCROOT/default_images/res/commandimagelist as no default_images subdirectory or link exists. The environment variable RSCDEFIMG is set in settings.mk to 'default_images'. Should this be some other value ? What did I miss ? Appreciate any help. Enno - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [dev] Built and now what ?
Jim, As usual your reply was quick and helpful. I am very grateful but also still confused. I got the impression from the OOo website that having downloaded solver and the one module, ie. sal, I want to build with debug=true I could get an OOo that would work under gdb. Now I think there are many more steps. The following is rather verbose but I believe it should grow into a page for solver newbies like me on the OOo website. Some of it may be right but please point out when I go astray. 1) Select a $SRCROOT directory 2) Download a solver tarball which unpacks into $SRCROOT/solver ( You can unpack somewhere else but then have to tell configure with --with-local-solver= ) 3) Checkout the project of interest, ie. porting (which includes module sal) AND solenv, installation, dmake, and possibly 4) cd $SRCROOT/config_office ./configure Creates bootstrap and the xxxEnv.Set scripts in $SRCROOT 5) cd $SRCROOT; source xxxEnv.Set bootstrap - creates platform specific files incl. dmake Now ready for repeated builds 6) To rebuild module sal: cd $SRCROOT; source xxxEnv.Set; cd sal build -u (The -u gives more output to find where things go wrong when they do) This compile/links a new sal library into the directory $SRCROOT/porting/sal//lib/libuno_sal.so.3 7) Make an installation set cd $SRCROOT; source xxxEnv.Set; cd installation/instset_oo export PKGFORMAT= (Not needed if platform default will do) build -u An installation set is a file or set of files describing all files needed to make an installation package for a particular product/ platform/ language (?) (Some kind of concatenation of .scp files ?) 8) Make a package based on the installation set Don't know yet. cd $SRCROOT; source xxxEnv.Set; cd ??? build -u 9) Get appropriate install script from an openoffice.org/developer mirror (Necessary once you have an .rpm package?) 10)Install the package in some directory eg. ~/ootrial running rpm -i --prefix=/home/me/ootrial Definitively the core package but maybe others? 11) Run ~/ootrial//soffice Find problem and back to 6) or live happy ever after. In 7) things go wrong for me. After some preliminaries error: find: /loc/prog32/oomodules/default_images/res/commandimagelist: No such file or directory There is no such file in solver so what does it solve. A 'commandimagelist' directory exists CVS repository [framework]/res Do I now also have to checkout the framework project? Even more? If 11) is the last step I am over halfway. Enno - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[dev] Built and now what ?
I think I got project sal rebuilt cleanly with debug=true. Then I wanted to check that I can run soffice from solver directly (before delivering the new libs into the output tree so that any problems could not be attributable to anything to do with the new libs). Entering $SRC_ROOT> solver/680/unxlngi6/bin/soffice gave a neat little window with the text The application cannot be started. An internal error has ocurred. The message is clear but the solution less so. I didn't find some 'setup' or whatever script. Anyway, I don't want to install over my ordinary 'operational' OO nor delete/overwrite its settings etc. How can I run the solver version completely separate from the operational one? Regards, Enno - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [dev] Extra build options
Jim Watson wrote:
A simple method is to set CC="/path/to/gcc -m32" and CXX="/path/to/g+
+ -m32" before running configure. Note the quotes ("). This works for
me building 32 bit on 64 bit machine for GNU/Linux SPARC (debian/
unstable) like CC="/usr/local/4.1/bin/gcc -m32" and it is easy to
switch to a different compiler. The configure step checks the
compiler and sets up some related paths.
Your suggestion works fine. In fact it also seems to work to define
CFLAGS="-m32" etc. before configure.
My next problem is that setso_env still recognizes my processor as
x86_64 type and gives me platform code unxlngx6. That clashes with the
solver I downloaded which contains the libs etc. for unxlngi6.
I pretended to be a ordinary i586 but then configure sets the platform
as unxlngi4.
I get the impression the '4' and '6' are for a gcc compiler version <
resp. >= 3.4.1
and I have currently installed 3.3.4 so unxlngi4 and still the wrong solver.
I am loath to try and install a newer gcc because I have several times
messed up my system by trying to update some bits and not other bits.
Now considering to forget about solver and recompile the whole caboodle
from source.
Is that likely to work or would I get into other problems because of my
'old' compiler.
Appreciate any views.
Enno
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
[dev] Extra build options
I run on a x86_64 system and to build 32-bit objects the compiler needs a -m32 option. I am trying to rebuild the sal module (initially to get debugging symbols). The first thing that build seems to do is create and execute a .cmd file to compile and link the typesconfig program. The Makefiles description page of the tools project indicates the use of environment variables ENVCFLAGS and ENVCXXFLAGS to add extra options, like my -m32, to the buildprocess. I have tried this and a few other things but I can't get the -m32 into the (generated) .cmd file. All help appreciated. Enno - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [dev] Where to find source code for X,,,
Will dig a bit further with strace. Sounds good idea. Thanks CPH. Jim, No, I did not use File-Recent Documents although my files obviously do appear there Enno On 01/11/2006, at 12:52 AM, CPHennessy wrote: ... Try strace Jim Watson wrote: ... are you using the File-Recent Documents to open the files? jim - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [dev] Where to find source code for X,,,
I believe the backup path must be valid because backups succeed when the main Save is to ordinary harddisk. Also I can save to USB stick when using a new name - manually entered in SaveAs dialog - so I have write permission for that path. Actually I usually have option 'Automatic backups' off. I write to USB stick exactly because I don't want copies on harddisk. The message Cannot create backup copy is the more irritating as I don't want a backup and the real save fails quietly. It is possibly something simple like you suggest but I don't see it (yet). Thanks. Jim Watson wrote: On 27/10/2006, at 11:03 PM, Enno Fennema wrote: I have two problems. Firstly, I can save a spreadsheet on a USB stick when using a new name so permissions appear to be ok. I can also later load that sheet from the USB stick but when I try to save it I get error message "Cannot create backup copy!!!" and nothing saved. I can save the spreadsheet with SaveAs under a new name. have a look in Tools - Options - OOo - Paths, are those paths all valid? jim - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [dev] Where to find source code for X,,,
I have two problems. Firstly, I can save a spreadsheet on a USB stick when using a new name so permissions appear to be ok. I can also later load that sheet from the USB stick but when I try to save it I get error message "Cannot create backup copy!!!" and nothing saved. I can save the spreadsheet with SaveAs under a new name. This problem only arises under SuSE Linux 9.2 x86_64. Running a pure 32 bit system everything works fine. I am quite happy to plod on and try to identify where things go wrong but that brings me to my second problem. I am a reasonably experienced programmer but have minimal experience in C++ and even less with the whole UNO setup. I find it very difficult to find what gets done where also as their appear to be directories in CVS outside Attic's that are no longer used (I think). My immediate question was therefor what procedure can I follow to find the source code for 1) store() and 2) for methods called from store() till I get down to the ucp or sal level. Is there LXR access to the repository? Appreciate any help. Enno Mathias Bauer wrote: Enno Fennema wrote: I would like to find out why my computer refuses to save OOo spreadsheets. It works fine for ordinary diskfiles but fails on my USB stick. I have been plodding through the Developers Guide and the CVS repository but am utterly confused. In the end I want the source code that is executed when call store() on a officedocument that implements an XStorable interface. I don't want a specific answer (might also be useful) but would like to know how to go about finding the answer myself. What path do I follow through the maze of projects/modules/directories/etc. If I haven't found the right document please refer me to it, otherwise any pointers appreciated. There is a lot of code executed when store() is called, any problems on file access most probably will happen in ucb/source/ucp/file or in the lowest file system access code in sal. Can you describe what exactly happens when you try to save to the stick? Nothing? Or do you get an error message and if you get one what does it tell? And can you load a file from the stick? Ciao, Mathias - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[dev] Where to find source code for X,,,
I would like to find out why my computer refuses to save OOo spreadsheets. It works fine for ordinary diskfiles but fails on my USB stick. I have been plodding through the Developers Guide and the CVS repository but am utterly confused. In the end I want the source code that is executed when call store() on a officedocument that implements an XStorable interface. I don't want a specific answer (might also be useful) but would like to know how to go about finding the answer myself. What path do I follow through the maze of projects/modules/directories/etc. If I haven't found the right document please refer me to it, otherwise any pointers appreciated. Enno Fennema - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
