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 path-to-package --prefix=/home/me/ootrial Definitively the core package but maybe others? Everything except desktop integration (i think) 11) Run ~/ootrial/bin or program or ../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]
Re: [dev] Built and now what ?
On 07/11/2006, at 10:30 AM, Jim Watson wrote: Enno, 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. Enno, i dont any other ideas. I am now downloading the 2.0.4 solver for linux/intel, and will reply again when I have tried it, jim - 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=abs-path-to-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 options 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/platform=unixlngi6.pro/lib/libuno_sal.so.3 7) Make an installation set cd $SRCROOT; source xxxEnv.Set; cd installation/instset_oo export PKGFORMAT=rpm (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 path-to-package --prefix=/home/me/ootrial Definitively the core package but maybe others? 11) Run ~/ootrial/bin or program or ../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]
Re: [dev] Built and now what ?
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? 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 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 path-to-package --prefix=/home/me/ootrial Definitively the core package but maybe others? Everything except desktop integration (i think) 11) Run ~/ootrial/bin or program or ../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]
Re: [dev] Built and now what ?
On 06/11/2006, at 4:03 AM, Enno Fennema wrote: 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? I usually build with rpm and install it into my home directory, as different versions live side-by-side, although they share one ~/.openoffice.org2 (and sometimes one .config ). You might save this somewhere, or you could consider working as a different user. The output tree does not contain a running installation, but it contains an installation package. This could be rpm, deb or something, it depends what you configured for example --with- package=rpm else it takes the default for the build platform distribution. You can re-package for rpm or whatever you like this way, there is no need to re-build. export PKGFORMAT=rpm cd instsetoo_native build The installation sets are in instsetoo_native/unxlngs.pro/ (product) / install/ (lang) There are three products OpenOffice.org, OpenOffice.org_SDK and URE You can move these somewhere to keep them safe in case you make a new one. I usually build with rpm and install it into my home directory, as different versions live side-by-side, although they share one ~/.openoffice.org2 (and sometimes one .config ). You might save this somewhere, or you could consider working as a different user. The install script is on mirrors in openoffice.org/developer/ install_scripts To create a new OOo installation in ~/m192 I run it like this with absolute paths $ ./install_linux.sh /path/to/rpm /home/jim/m192 There are other ways and some probably better, but this will get you started quickly. Look in instsetoo_native/util/makefile.mk for more options. You can build the different targets in there, using dmake. There are some improvements on the way, that will create a ready to run installation. jim - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
