Re: Update to python-2.17

Hi all, I have replaced everything 2.7.17 to 2.7.18. Added the Python file in downloads. I would do now a test build. After the test build how can I test if there are issues? All the best Peter Am 21.04.20 um 18:40 schrieb Matthias Seidel: Hi Marcus, Am 21.04.20 um 18:33 schrieb Marcus

Re: Update to python-2.17

I agree. We should ensure that all works w/ 2.7.18 since it is the last of the Python 2.7s... even if it means we "fix" AOO to work with it, we should simply baseline that version. > On Apr 21, 2020, at 7:56 AM, Matthias Seidel > wrote: > > Hi all, > > The final Python 2.7.18 is out: > > ht

Re: Update to python-2.17

Hi Jim, Am 23.04.20 um 13:42 schrieb Jim Jagielski: > I agree. We should ensure that all works w/ 2.7.18 since it is the last of > the Python 2.7s... even if it means we "fix" AOO to work with it, we should > simply baseline that version. In trunk and AOO42X we are already on 2.7.17. No problems

Re: Update to python-2.17

Hi Peter, Am 23.04.20 um 10:04 schrieb Peter Kovacs: > Hi all, > > > I have replaced everything 2.7.17 to 2.7.18. Added the Python file in > downloads. > > I would do now a test build. Great! > > After the test build how can I test if there are issues? Simply run the Python scripts in Writer. Tha

Re: Update to python-2.17

> On Apr 23, 2020, at 8:50 AM, Matthias Seidel > wrote: > > Hi Jim, > > Am 23.04.20 um 13:42 schrieb Jim Jagielski: >> I agree. We should ensure that all works w/ 2.7.18 since it is the last of >> the Python 2.7s... even if it means we "fix" AOO to work with it, we should >> simply baselin

Re: Update to python-2.17

Hi Jim, Am 23.04.20 um 15:21 schrieb Jim Jagielski: > >> On Apr 23, 2020, at 8:50 AM, Matthias Seidel >> wrote: >> >> Hi Jim, >> >> Am 23.04.20 um 13:42 schrieb Jim Jagielski: >>> I agree. We should ensure that all works w/ 2.7.18 since it is the last of >>> the Python 2.7s... even if it means

Re: about build environment development

IMO, dmake is simply a build-and-compile dependency. Considering that we pull in lots of other external dependencies, keeping or dropping dmake will likely not make any real difference in the people we can attract to help develop, test and build AOO. At the very least, we know what dmake is good

Re: about build environment development

Hi Jim, dmake is not simple. I do know nothing Jim Jagielski... Today the build system enjoys me with checking whether the found dmake is the right dmake... configure: WARNING: no or configure: error: no URL for dmake source code specified, either. Use --with-dmake-url to supply an URL;

Re: about build environment development

On 4/23/20 10:44 AM, Peter Kovacs wrote: Hi Jim, dmake is not simple. I do know nothing Jim Jagielski... Today the build system enjoys me with checking whether the found dmake is the right dmake... configure: WARNING: no or configure: error: no URL for dmake source code specified, eith

Re: about build environment development

fixed my issues. Jim, I had an install issue with latest trunk of your epm repo: make: INSTALL@: Befehl nicht gefunden (command not found) Makefile:153: die Regel für Ziel „install“ scheiterte (install failed) make: *** [install] Fehler 127 I think some sort of typo maybe? 4.4.2 works good.

Problem building Cui in Trunk

Build broke with = Building module cui = Entering /home/legine/workspace/AOO/gitbox/main/cui/prj cd .. && make -s -r -j1   && make -s -r deliverlog /home/legine/workspace/AOO/gitbox/main/cui/Library_cui.mk:37: *** missing separator.  Stop. dmake:  Error code 2, while m

Issue in vbahelper

Hello all, Build broke again, this time with Following Output: = Building module vbahelper = Entering /home/legine/workspace/AOO/gitbox/main/vbahelper/prj cd .. && make -s -r -j1   && make -s -r deliverlog [ info  ALL ] LinkTarget Library/libmsfilter.s

Issue in desktop?

Okay, I try to sit this out by restart the build. Guessing it is a possible dependency breaker. = Building module desktop = Entering /home/legine/workspace/AOO/gitbox/main/desktop/test/deployment/boxt mkout -- version: 1.8 Making:    all_test_deployment_boxt.dpslo Comp

Re: Problem building Cui in Trunk

Okay the colon was not the issue. :/ Am 24.04.20 um 05:09 schrieb Peter Kovacs: Build broke with = Building module cui = Entering /home/legine/workspace/AOO/gitbox/main/cui/prj cd .. && make -s -r -j1   && make -s -r deliverlog /home/legine/workspace/AOO/gitbox/main/cu

Re: Problem building Cui in Trunk

lol Google gives: As indicated in the online manual, the most common cause for that *error* is that lines are indented with whitespaces when |make| expects tab characters. Correct target:\tcmd where \t is TAB Wrong target:cmd Anyways, I figured that build -v in the module gives a debug

Re: Issue in vbahelper

On Fri, Apr 24, 2020 at 5:18 AM Peter Kovacs wrote: > Hello all, > > Build broke again, this time with Following Output: > > = > Building module vbahelper > = > > Entering /home/legine/workspace/AOO/gitbox/main/vbahelper/prj > > cd .. && make -s -r -j1

Re: Issue in vbahelper

I have not seen an error in filter. I had issues in, but not posted to the list: = Building module scripting = and = Building module sc = restart did work around all issue except on Cui. There I commented the problematic build lines, and the bu

Re: Update to python-2.17

Hi all, My test build has been successful and I was able to execute a python code. This afternoon I hope I can push the changes for the migration to github for review. All the best Peter Am 23.04.20 um 15:24 schrieb Matthias Seidel: Hi Jim, Am 23.04.20 um 15:21 schrieb Jim Jagielski: O