I download SDK and start it's index.html
The link 'C++ reference' points to file:///<myinstall>/sdk/docs/cpp/ref/index.html
But a subfolder cpp does not exist, neither in 'docs' nor elsewhere.
The link 'License' points to file:///<myinstall>/sdk/share/readme/LICENSE_en-US.html
But that file does not exist. There are the files license.txt and readme_en-US.txt
Can you advise on where you are downloading the SDK From. We will also need to know which operating system you are attempting to install it on
Bug is reproducible with LibO-SDK_3.6.1_Win_x86_install_multi.msi. "c:\Program Files\LibreOffice 3.6\sdk\docs\cpp" is missing. However, on Linux master it is there, az least it is built into the odkcommon.zip in odk/unxlngx6.pro/bin/. So further investigations are needed.
We have two issues here.
1. Missing cpp documentation. That is because release builds on Windows are configured --without-doxygen. Fridrich can tell why it is so, and he can install doxygen to build server.
2. Wrong link to license. I guess it never worked. The problem is that readme and license are called different names under Linux and Windows. I wonder why. Another problem is that we need a short version of the license text, the license of SDK is LGPLv3 I suppose, no need to include the full text including licence of fonts, dictionaries, third party libs etc. I CC Michael, just in case. Maybe we should link MPLv2 when we make the move.
I installed cygwin's doxygen on the builder machine. Will run a partial rebuild just to find out whether it works like that
Chunks of the SDK are BSD licensed; so I'd feel happier shipping the entire license file with it automatically if possible - particularly as we move to MPLv2 on ALv2 with some BSD bits etc.
Andras Timar committed a patch related to this issue.
It has been pushed to "master":
fdo#50936 fix link to license file in SDK documentation
The patch should be included in the daily builds available at
http://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More
information about daily builds can be found at:
Affected users are encouraged to test the fix and report feedback.
Setting to fixed, since it is in LO 4.0