Hi Steven,
Thankz for answer,
Now some other question :)
I got these error when compiling.
file M:\QT\Pdf_Tex\texstudio_svn\buildmanager.obj(buildmanager.obj):
undefined symbol __Z21getCommandLineViewDviv
file M:\QT\Pdf_Tex\texstudio_svn\buildmanager.obj(buildmanager.obj):
undefined symbol __Z20getCommandLineViewPsv
file M:\QT\Pdf_Tex\texstudio_svn\buildmanager.obj(buildmanager.obj):
undefined symbol __Z29getCommandLineViewPdfExternalv
file M:\QT\Pdf_Tex\texstudio_svn\buildmanager.obj(buildmanager.obj):
undefined symbol __Z25getCommandLineGhostscriptv
He ask cause thats the cause from those errors:
Need some default values for the command lines
Is there a define to check for os/2? Then you could give me the
command lines you use, and I add them there
On Tue, 11 Sep 2012 23:29:57 UTC, "Steven Levine"
Post by Steven LevineHi Elbert,
Post by TeLLieAny knows if OS/2 uses signals like unix or structured exception
handlers like Windows to kill
programs after segmentation faults?
OS/2 has it's own exception management subsystem. In simple terms,
the exception management subsystem arranges to call one or more
exception handlers in response to a given exception. An exception
handler can handle the exception or pass it on to the next handler in
the chain. Logically there is a default, kernel supplied exception
handler at the end of the chain. This is the handler that generates
the popuplog entry and kills the process.
The OS/2 exception handler interface is pretty flexible so some
runtimes, such as kLIBC, map the OS/2 exceptions to the unix style
exceptions that applications expect to receive. This means that a
port application can use signal() and it will operate almost excactly
like it would in unix.
Steven
--