I tried to create dmg installation file from a local branch in terminal getting
following errors:
[build ALL] All modules but instset: UnoControls accessibility animations
apple_remote avmedia basctl basegfx basic bean binaryurp bridges canvas chart2
cli_ure codemaker comphelper configmgr conne
I tried to build a local branch created by merging latest gerrit master with
another branch, on both Ubuntu 16.04.4 and Ubuntu 18.04.1, and got the same
following error.
No core file identified in directory
/home/dev/libreoffice/workdir/CppunitTest/sd_import_tests.test.core
To show backtraces
Hello, I just finished merging an old branch for TB_LR writing support in last
3 months, and can only build with:
--enable-dbgutil (not --enable-debug) in autogen.input and
make build-nocheck
on macOS 10.13. Furthermore, I asked about "build check" here months ago, but
haven't got a resolution
>I have no idea, but if all you want is for VS Code to run the same commands
>that you would otherwise enter yourself, you need to run ./autogen.sh first,
>at least once, before you can run make.
I want to get rid of "cannot find source file..." errors in problem panel and
jiggles in source fi
I want to build LO in VS Code on Mac.
Though "${workspaceFolder}" was set in browse.path and includePath in
$LODE_HOME/dev/core/.vscode/c_cpp_properties.json,
there are many "cannot open source file..." in problem panel and many #include
are underlined with jiggles.
By searching on Internet, I le
1. git fetch origin && git reset --hard origin/master
2. autogen.input:
--enable-dbgutil
--enable-debug
--enable-symbols
--disable-cve-tests
--without-junit
--with-build-version=$(date +"MacD%Y-%m-%d")
--with-vendor=Almas Inc.
--enable-scripting-javascript
#EOF
#comment: because I've always failed
e $LODE_HOME and start over from the very beginning again or how
to get make work?
____
From: tlillqv...@gmail.com on behalf of Tor Lillqvist
Sent: Monday, April 2, 2018 5:54 PM
To: Ch g
Cc: Noel Grandin; libreoffice@lists.freedesktop.org
Subject: Re: make fails on M
/llvm/6.0.0/include/clang/AST/RecursiveASTVisitor.h
/usr/local/Cellar/llvm/6.0.0/include/llvm/Support/Valgrind.h
/usr/local/Cellar/llvm/5.0.1/include/clang/AST/RecursiveASTVisitor.h
/usr/local/Cellar/llvm/5.0.1/include/llvm/Support/Valgrind.h
/Library/Developer/CommandLineTools/SDKs/MacOSX.sdk/usr/i
d by law.
Will I better off "reset hard", then "make && make install", and only after
make succeeded, start over(do from the beginning?) cherry-pick?
From: Heiko Tietze
Sent: Thursday, March 29, 2018 10:33 PM
To: Ch g; libreoffice@lis
Hello all, I first built LO official source successfully with "build-nocheck"
option in this January, and could start that built
app. But last week, I cherry-picked 3 commits from a forked repo which enabled
vertical Mongolian editing, then make failed with errors occurred in unedited
files. So
10 matches
Mail list logo
