Home » Developing U++ » UppHub » OCE exit problem
| OCE exit problem [message #40686] |
Mon, 02 September 2013 13:11  |
keltor
Messages: 73
Registered: February 2012
|
Member |
|
|
Hello uppers,
I have been testing some old application that contains the nice OCE package provided by Max. I tried compiling it and it worked fine, but when I ran it, it crashed on exit. To my surprise, even the OCETest crashed on me when I close it.
I managed to get OCETest working only by compiling it under MSC9 or, to be more exact, using the Windows SDK package that U++ suggests to install when it is first run. My application closes fine too but only after substituting any Break() with exit().
I am a little afraid to do this change. Could it be a source of leaks? Has anybody else had any trouble/any solution?
Puzzled,
Kel
|
|
|
|
|
|
| Re: OCE exit problem [message #41772 is a reply to message #41163] |
Sat, 18 January 2014 10:23  |
mdelfede
Messages: 1308
Registered: September 2007
|
Ultimate Contributor |
|
|
Hi Keltor,
OCC/OCE are changing license to LGPL, so static build is no more an option for me.... and for everyone which wants to build a closed source application.
So I'm trying to create a new package for dynamic building.
You could use the provided one, but it's annoying on windows, and requires cmake/nmake and a proper build system. And it builds some 60+ dlls....
Using pre-built libs is not an option for me, they're tied to a specific compiler version.
I was ready with linux single dll package, but it doesn't build on windows because of limit of 64K symbols on a single dll.
I'm thinking on a solution with just a couple of dlls, I'll post it when ready with updated demo.
Ciao
Max
|
|
|
|
Goto Forum:
Current Time: Wed Dec 04 16:33:36 CET 2024
Total time taken to generate the page: 0.02239 seconds
|
Members
Pages
Help
Register
Login
Home
