The LiveCD to Debian migration Howto

Hi,

because I don't want to reboot my computer all the time because it disrupts my workflow I tried and so far succeded in installing the Salome system on my debian testing. Just do the following:

Build a kernel with squashfs. The patch for the kernel is in the Debian package system.

Reboot, mount the DVD and loopback mount the system image:
Kapitaen:/home/totty# mount /cdrom
Kapitaen:/home/totty# mount -o loop -t squashfs /cdrom/livecd.sqfs /mnt

Copy the relevant part to your harddisk (1.5GB):

Kapitaen:~/$ mkdir SalomeCD
Kapitaen:~/$ cd SalomeCD
Kapitaen:~/SalomeCD$ cp -r /mnt/opt/* .

Edit ~/SalomeCD/salome/Salome.sh

#!/bin/bash
#source /opt/salome/KERNEL_2.2.2/salome.sh
#/opt/salome/KERNEL_2.2.2/bin/salome/runSalome
source ~/SalomeCD/salome/KERNEL_2.2.2/salome.sh
~/SalomeCD/salome/KERNEL_2.2.2/bin/salome/runSalome

Edit ~/SalomeCD/salome/KERNEL_2.2.2/salome.sh at the beginning

#export INSTALL_ROOT=/opt/salome
export INSTALL_ROOT=~/SalomeCD/salome

do some symlinks in /usr/lib

Kapitaen:/usr/lib# ln -s libssl.so libssl.so.2
Kapitaen:/usr/lib# ln -s libcrypto.so libcrypto.so.2

try:

Kapitaen:~/SalomeCD$ ./Salome.sh

It is possible that it only works for me because I tried unsuccessfully to compile Salome before and therefore some necessary tools might be on my system but not on yours.
So far I could mesh a step file.

Way cool,

Cheers, Torsten

P.S. What does this in the startup mean:
th. 3030354864 - Trace ../../../KERNEL_SRC/src/NamingService/SALOME_NamingServic
e.cxx [337] : Resolve() : Registry (object) not found

P.P.S. What do the errors mean when I save:
th. 2987624704 - Trace ../../../KERNEL_SRC/src/LifeCycleCORBA/SALOME_LifeCycleCO
RBA.cxx [106] : Catalog Error : Component not found in the catalog
th. 2987624704 - Trace ../../../KERNEL_SRC/src/LifeCycleCORBA/SALOME_LifeCycleCO
RBA.cxx [106] : Catalog Error : Component not found in the catalog
th. 2987624704 - Trace ../../../SMESH_SRC/src/SMESH_I/SMESH_Gen_i.cxx [779] : SM
ESH_Gen_i::Save
th. 2987624704 - Trace ../../../SMESH_SRC/src/SMESH_I/SMESH_Gen_i.cxx [1507] : S
MESH_Gen_i::Save() completed
th. 2987624704 - Trace ../../../KERNEL_SRC/src/LifeCycleCORBA/SALOME_LifeCycleCO
RBA.cxx [106] : Catalog Error : Component not found in the catalog
th. 2987624704 - Trace ../../../KERNEL_SRC/src/LifeCycleCORBA/SALOME_LifeCycleCO
RBA.cxx [106] : Catalog Error : Component not found in the catalog
th. 2987624704 - Trace ../../../SMESH_SRC/src/SMESH_I/SMESH_Gen_i.cxx [779] : SM
ESH_Gen_i::Save
th. 2987624704 - Trace ../../../SMESH_SRC/src/SMESH_I/SMESH_Gen_i.cxx [1507] : S
MESH_Gen_i::Save() completed
th. 2987624704 - Trace ../../../KERNEL_SRC/src/VTKViewer/VTKViewer_ViewFrame.cxx
[142] : VTKViewer_ViewFrame::~VTKViewer_ViewFrame()

P.P.P.S. Could you explain how you got it to build or was it just a question of EXACTLY the right distro?

Hi Torsten,

good to see that we can more or less simply transfer binaries to make it work: sounds good for future packages.

For your first PS: It's \"normal\" or more precisely \"usual\"...

PPS: I am sorry, I had no time to look at it, but I will try to have see if I have the same error messages (to my opinion Salome 2.2 is still in a Beta stage, so you can see a lot of \"meaningless\" error messages...)

PPPS:
To make it short (and also because I don't remember all the details now ) for Salome, I just took the Binary CD Image, extracted the ISO in a temp directory, installed g++, g77, and run the compilation script. I have chosen a custom build and selected all binaries when possible. I only had a problem with DOxygen, but I doesn't seem a problem. Maybe I forgot some \"important\" details, but I will write a complete HowTo for SALOME v3 (to be released in Jan. 2006).
For Code-Aster, I have installed (binaries) blas, lapack, g77, python-devel and followed their custom compilation procedure. Then, you need some time to configure ASTK & STANLEY correctly, but for this you can just copy the settings from /root/.ASTKrc of the LiveDVD. And NO, it's not a question of distro, ASTER can be built on almost any Unix thanks to it's custom compilation script. But I must admit that Salome is a bit tricky to compile, even with 90% of the pre-requisite binary libraries...

Thanks for your HowTo !!

Great work,

I succeded with the piston tutorial. I would just like to add that installing aster from source is easier than moving aster from the CD. Just edit setup.cfg for the destination and run python setup.py install and install any missing prerequisite libraries.

Cheers, Torsten

It's also easy to do this from the virtual machine.

1) tar whatever files you want (why not everything in /opt?).
2) sftp them to a neutral computer, then onto your own

Like this guy, I already had everything on Salome's 'Software Requirements' page installed. Aster was no problem to install from source. For whatever reason Salome is the least open open-source program I've run across.
-b