- Index
- » Usage and Applications
- » OpenModelica Usage and Applications
- » Sucess build, failure to run OMEdit &...
Sucess build, failure to run OMEdit & OMOptim
Sucess build, failure to run OMEdit & OMOptim
The trunk (rev 8488) builds cleanly on an ArchLinux64 system.
gcc -v:
>> gcc version 4.5.2
make -v
>> GNU Make 3.81
binutils 2.21
omniorb 4.1.4
The application 'omc', 'OMEdit' and OMNotebook starts as expected and
seems to function well from my limited testing.
Starting OMEdit:
"""
Application asked to unregister timer 0x1e000006 which is not registered in this thread. Fix application.
Application asked to unregister timer 0x3e000007 which is not registered in this thread. Fix application.
Application asked to unregister timer 0x6a000010 which is not registered in this thread. Fix application.
"""
DialogBox Error:
"""
Unable to find OMEdit server, Object reference file
/tmp/openmodelica.rute.objid.OMEdit210137269 not created.
"""
OMEdit fails to start after a dialog box twice report error in finding
the Corba IOR file in the system 'tmp' folder.
Starting OMOptim:
"""
Object::connect: No such slot MainWindow::showTabTitlePopup(const QPoint &)
Object::connect: (receiver name: 'MainWindowClass')
"""
Log:
"""
Unable to find OMEdit server, Object reference file /tmp/openmodelica.rute.objid.OMOptim210918 not created.
Unable to communicate with OMC
"""
OMOptim fails to operate correctly.
For earlier revision of the repo there was a similar error for OMShell which
was 'fixed' by removing a trailing '.' in the Corba IOR file. These error seems
to be related as omc clearly starts correctly for other applications.
Best regards
Runar Tenfjord
Re: Sucess build, failure to run OMEdit & OMOptim
But thanks for the bug-report. I will see if I can resolve this tomorrow.
I would guess OMOptim does not null-terminate the name of the expected file (trailing garbage digits). Regardless, OMOptim on Linux can only be used to try out the GUI right now. Launching simulations (and thus doing optimizations based on simulation results) sadly uses WIN32 API.
- sjoelund.se
- 1700 Posts
Re: Sucess build, failure to run OMEdit & OMOptim
Either try r8493 (where the OPENMODELICAHOME from the configure script is used). Or launch the process as OPENMODELICAHOME=/path/to/trunk/build OMOptim.
At least I am guessing this is your issue. If you still have problems, just post them here and I will try to respond.
- sjoelund.se
- 1700 Posts
Re: Sucess build, failure to run OMEdit & OMOptim
I found the error. The error was not fixed in r8493. My environment variable
'OPENMODELICAHOME' was defined without a trailing slash and in
OMCProxy.cpp 'bin/omc' is append to the variable giving an non existing
path.
Perhaps a simple check if the path to omc should be added or that
a trailing slash is added if needed. Probably the same error for OMOptim.
Runar
Re: Sucess build, failure to run OMEdit & OMOptim
Thanks. I guess it would have been fix if you had OPENMODELICAHOME unset (this is what the Ubuntu builds use, so I don't test OPENMODELICAHOME as heavily as I used to).
But this should be fixed now.
- sjoelund.se
- 1700 Posts
- Index
- » Usage and Applications
- » OpenModelica Usage and Applications
- » Sucess build, failure to run OMEdit &...