Date: prev next · Thread: first prev next last
2012 Archives by date, by thread · List index


On 02/22/2012 01:50 PM, Martin Thoma wrote:
Are you building that SimpleBootstrap_cpp example with the 3.4.5 SDK,
with the 3.5 SDK, or with a hand-crafted build environment of your own?
So far with a hand-craftet build environment for Microsoft Visual Studio.

For 3.5, LO's basis and brand layers have been re-merged into a single
layer, so the paths of lots of files within the LO installation have
changed.
It doesn't seem to be so complicated: In the past you had to know the pathes
of the rdb-files to make cppumaker run to generate the header-files. Then we
added the pathes of the DLLs needed to PATH, define CPPU_ENV=msci, and well:
We were able to connect without problems.

In the past, if we did something wrong here, there was a "could not include
file" or "DLL not found" error, but now everything compiles without warnings
or errors (so the headers should be ok) and the DLLs are found and loaded
correctly as well. I do not exclude that we made something wrong, but
without a kind of "changelog" or a clear error-message, I'm a bit stuck here
how to isolate the problem.

Yeah, but as you are "messing around" with the internals, all I can offer you is "have a look into the code." The high-level changelog is "lots of paths changed due to layer merging" and the low-level changelog is the git logs---there's unfortunately nothing in-between that might be of help to you.

Stephan

Context


Privacy Policy | Impressum (Legal Info) | Copyright information: Unless otherwise specified, all text and images on this website are licensed under the Creative Commons Attribution-Share Alike 3.0 License. This does not include the source code of LibreOffice, which is licensed under the Mozilla Public License (MPLv2). "LibreOffice" and "The Document Foundation" are registered trademarks of their corresponding registered owners or are in actual use as trademarks in one or more countries. Their respective logos and icons are also subject to international copyright laws. Use thereof is explained in our trademark policy.