Thanks, you're right, with one repo, the checkout and build process is definitely much smoother!
(1) I had to comment out some code in qa\osl\security\osl_Security.cxx because it was trying to run a unit test which failed because I'm not logged in as Administrator. Perhaps it should skip that test if the currently logged in user is not Administrator? (2) I have to do "export DISABLE_ATL=true" because otherwise I get a compile fail in embedserve, I don't appear to have the atlbase.h file on my machine. Perhaps this should be a configure check? (3) Right now I'm struggling to get past a link error in l10ntools helpmerge.obj : error LNK2019: unresolved external symbol "__declspec(dllimport) class rtl::OString __cdecl comphelper::string::getToken(class rtl::OString const &,long,char)" Any ideas? Thanks, Noel Grandin Tor Lillqvist wrote: >> Are there up-to-date instructions somewhere for building on Windows with the >> new OneGit repos? > Well, the aspects that changed with the switch from several git repos to just > one (or two, or three, depending on whether you want to include help and > dictionaries or not) don't differ between platforms... So just clone the new > "core" repo, and build using old instructions. Please report specific errors > you get... > > --tml > > > _______________________________________________ > LibreOffice mailing list > LibreOffice@lists.freedesktop.org > http://lists.freedesktop.org/mailman/listinfo/libreoffice > Disclaimer: http://www.peralex.com/disclaimer.html
_______________________________________________ LibreOffice mailing list LibreOffice@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice
