Re: Difficulty with dmake

[Damjan Jovanovic]

I am not sure. My changes definitely didn't affect that.

I think it might have always been the case, that "source ..." is necessary
before ./bootstrap.

On Thu, Jan 26, 2017 at 6:39 AM, Patricia Shanahan  wrote:

> Thanks. That worked.
>
> The step-by-step puts winenv.set.sh after ./bootstrap, and that used to
> work. Do you expect it to work again, or do we need to edit the
> instructions?
>
>
> On 1/25/2017 8:25 PM, Damjan Jovanovic wrote:
>
>> Try "source winenv.set.sh" between ./configure and ./bootstrap.
>>
>> Damjan
>>
>> On Thu, Jan 26, 2017 at 2:20 AM, Patricia Shanahan  wrote:
>>
>> I am trying to set up a new debug environment, incorporating the recent
>>> changes to how debug works. Unfortunately, my configure-and-bootstrap
>>> cannot find dmake. It looks for it in a different URL from the one
>>> specified as DMAKE_URL from configure.
>>>
>>> run_configure.sh contains my configure parameters. wk_log.txt is the
>>> output from an attempt to configure and bootstrap.
>>>
>>>
>>> -
>>> To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
>>> For additional commands, e-mail: dev-h...@openoffice.apache.org
>>>
>>>
>>
> -
> To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
> For additional commands, e-mail: dev-h...@openoffice.apache.org
>
>

Re: Difficulty with dmake

[Patricia Shanahan]

Thanks. That worked.

The step-by-step puts winenv.set.sh after ./bootstrap, and that used to 
work. Do you expect it to work again, or do we need to edit the 
instructions?


On 1/25/2017 8:25 PM, Damjan Jovanovic wrote:

Try "source winenv.set.sh" between ./configure and ./bootstrap.

Damjan

On Thu, Jan 26, 2017 at 2:20 AM, Patricia Shanahan  wrote:


I am trying to set up a new debug environment, incorporating the recent
changes to how debug works. Unfortunately, my configure-and-bootstrap
cannot find dmake. It looks for it in a different URL from the one
specified as DMAKE_URL from configure.

run_configure.sh contains my configure parameters. wk_log.txt is the
output from an attempt to configure and bootstrap.


-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org





-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org

Re: Difficulty with dmake

[Damjan Jovanovic]

Try "source winenv.set.sh" between ./configure and ./bootstrap.

Damjan

On Thu, Jan 26, 2017 at 2:20 AM, Patricia Shanahan  wrote:

> I am trying to set up a new debug environment, incorporating the recent
> changes to how debug works. Unfortunately, my configure-and-bootstrap
> cannot find dmake. It looks for it in a different URL from the one
> specified as DMAKE_URL from configure.
>
> run_configure.sh contains my configure parameters. wk_log.txt is the
> output from an attempt to configure and bootstrap.
>
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
> For additional commands, e-mail: dev-h...@openoffice.apache.org
>

Re: svn commit: r1780202 - /openoffice/trunk/main/README

[Pedro Giffuni]

Hi Marcus;

On 01/25/17 23:41, Marcus wrote:



In general the addition is OK. However, there is not yet agreement what
"supported" means. So, just to add FreeBSD to the list doesn't work as
it's not the same as for Win, Linux, Mac where we have a different
definition.

Marcus


I avoided making comments on things that have not been decided (and
that may even not ever be decided).

I think there is clear consensus that FreeBSD is in some way supported
and that Windows deserves to be in the top of the list.

For all I know we do more testing on FreeBSD than on MacOS so I placed 
it there but I admitted it is something subjective.


Feel free to make any other adjustment or clarification before 4.2.0
is released.

Regards,

Pedro.

-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org

Difficulty with dmake

[Patricia Shanahan]

I am trying to set up a new debug environment, incorporating the recent 
changes to how debug works. Unfortunately, my configure-and-bootstrap 
cannot find dmake. It looks for it in a different URL from the one 
specified as DMAKE_URL from configure.


run_configure.sh contains my configure parameters. wk_log.txt is the 
output from an attempt to configure and bootstrap.
SDK_PATH="/cygdrive/c/Program Files/Microsoft SDKs/Windows/v7.0"
./configure \
 --enable-dbgutil \
 --enable-symbols \
 --disable-strip-solver \
--with-frame-home="$SDK_PATH" \
--with-psdk-home="$SDK_PATH" \
--with-midl-path="$SDK_PATH/bin" \
--disable-directx \
--with-ant-home="/cygdrive/c/ant" \

--with-dmake-url="https://sourceforge.net/projects/oooextras.mirror/files/dmake-4.12.tar.bz2;
 \

--with-epm-url="https://sourceforge.net/projects/oooextras.mirror/files/epm-3.7.tar.gz;
 \
--disable-pch \
--disable-atl \
--disable-activex \
--without-junit \
--with-package-format="archive installed" \
--with-jdk-home="/cygdrive/c/Program Files (x86)/Java/jdk1.7.0_79"

Patricia@Jan2014Desktop /cygdrive/c/OpenOfficeDev/new_debug/main
$ source run_configure.sh
checking whether configure is up-to-date... yes

*  *
*   Apache OpenOffice build configuration. *
*  *
*   The configure process checks your platform to see whether  *
*   you can build Apache OpenOffice on it. *
*   This process checks all pre-requisites and generates a file*
*   containing the necessary environment variables.*
*   Source this file after configure has ended successfully.   *
*  *
*   Warnings that are generated during the configure process   *
*   must be taken into account since it can be a reason for*
*   an unsuccessful build of Apache OpenOffice.*
*  *



*  *
*   Checking the platform pre-requisites.  *
*  *


checking for grep that handles long lines and -e... C:/cygwin32/bin/grep.exe
checking for egrep... C:/cygwin32/bin/grep.exe -E
checking for gawk... gawk
checking for gawk... /usr/bin/gawk
checking for sed... /usr/bin/sed
checking for solenv environment... default
checking for custom pack.lst... no
checking build system type... i686-pc-cygwin
checking host system type... i686-pc-cygwin
checking target system type... i686-pc-cygwin
cygwin
checking Cygwin version... 2.4.1(0.293/5/3)
head: cannot open '/etc/*-release' for reading: No such file or directory
CYGWIN_NT-6.3-WOW Jan2014Desktop 2.4.1(0.293/5/3) 2016-01-24 11:24 i686 Cygwin
checking for pkg-config... /usr/bin/pkg-config
checking pkg-config is at least version 0.9.0... yes
checking whether to enable crashdump feature... no
checking whether to use the standard non-optimizing compiler... no
checking whether to build/use the Windows 64bit shell extensions... no
checking whether to turn warnings to errors... no
checking whether to do a debug build... no
checking whether to build with additional debug utilities... yes
checking whether to include symbols into final build... yes
checking whether to strip the solver or not no
checking whether to enable category B components... no: disabled modules nss, 
hunspell, hyphen, saxon, rhino, graphite, coinmp
checking whether to enable the Online Update support... yes
checking whether to enable unit tests... yes
checking whether to enable native CUPS support... no
checking whether to enable fontconfig support... no
checking whether to use DirectX... no
checking whether to use ActiveX... no
checking whether to use ATL... no
checking whether to use RPATH in shared libraries... yes
checking whether to use dicts from external paths... no
checking Windows build environment sanity... ok
checking for cygwin gcc/g++... found
checking for bash... /usr/bin/bash
checking gcc home... /usr
checking whether to enable pch feature... no
checking for GNU make... make
checking the GNU make version... make 4.1
3+:
checking for dmake... configure: no system or user-provided dmake found
dmake will be downloaded and compiled in bootstrap
checking for GNU or compatible BSD tar... tar
checking for perl... C:/cygwin32/bin/perl
checking the Perl version... checked (perl 5)
checking for required Perl modules... all modules found
checking for 

Re: svn commit: r1780202 - /openoffice/trunk/main/README

[Marcus]

In general the addition is OK. However, there is not yet agreement what 
"supported" means. So, just to add FreeBSD to the list doesn't work as 
it's not the same as for Win, Linux, Mac where we have a different 
definition.


Marcus



Am 25.01.2017 um 16:07 schrieb p...@apache.org:

Author: pfg
Date: Wed Jan 25 15:07:48 2017
New Revision: 1780202

URL: http://svn.apache.org/viewvc?rev=1780202=rev
Log:
Add FreeBSD to the list of supported platforms.

While here adopt some, admitedly subjective, order of importance according
to the expected support level.


Modified:
openoffice/trunk/main/README

Modified: openoffice/trunk/main/README
URL: 
http://svn.apache.org/viewvc/openoffice/trunk/main/README?rev=1780202=1780201=1780202=diff
==
--- openoffice/trunk/main/README (original)
+++ openoffice/trunk/main/README Wed Jan 25 15:07:48 2017
@@ -14,8 +14,9 @@ Apache OpenOffice (AOO)

 Currently supported platforms include:

+Microsoft Windows
 Linux variants
-Windows
+FreeBSD
 Mac OS X
 OS/2



-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org

Re: Chromebook Compatibility

[Hagar Delest]

FWD to OP, not subscribed to the list.

Hagar

Le 24/01/2017 à 16:51, FR web forum a écrit :

https://forum.openoffice.org/en/forum/viewtopic.php?f=6=78706=chromebook

- Mail original -
De: "Conner Holt" 
À: dev@openoffice.apache.org
Envoyé: Mardi 24 Janvier 2017 16:02:52
Objet: Chromebook Compatibility




I’m trying to find out if Open Office will work on the Chromebook OS. If it 
does please let me know. If not it could be a great opportunity to look into 
because Microsoft does not offer any of its suite to Chromebook except the 
online version. There is no way to edit your documents that are local except 
Google Docs which is very basic. I look forward to hearing back from you.



Conner Holt

Technical Department l Warranty |Sales

Pioneer Dock Equipment

1-800-337-6595 Direct Line

1-866-728-6195 Tech Support Line

1-931-486-0316 Fax

conn...@pioneerleveler.com

1x1 HP Series1x1 EVR650 Restraint


-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org




-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org

Re: AOO debugging revamp

[Don Lewis]

On 25 Jan, Damjan Jovanovic wrote:
> Hi
> 
> For a while I've noticed how gbuild modules don't have debug symbols unless
> built with the maximum debug level ("./configure --enable-debug" globally
> or "build debug=true" per module) which also produces oceans of log
> messages we usually don't want.
> 
> In r1780246, I've finally changed debugging in gbuild to match how dmake
> works: --enable-symbols and --enable-crashdump now also add debug symbols
> to gbuild modules like they do to dmake modules, and the
> --enable-symbols=small option is also implemented for GCC and Clang (sorry
> Windows developers, MSVC doesn't seem to have it). The only extra benefit
> of --enable-debug on top of this now, is that it disables compiler
> optimizations - should we disable them for --enable-symbols too?

I would say no.  Consider the case where there is a crash when the code
is compiled with optimization, but not when the code is compiled without
optimization.  Having the symbols for the former case is still useful
for finding the location of the crash even if a lot of the variables
that you might want to look at are optmiized out.


-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org

AOO debugging revamp

[Damjan Jovanovic]

Hi

For a while I've noticed how gbuild modules don't have debug symbols unless
built with the maximum debug level ("./configure --enable-debug" globally
or "build debug=true" per module) which also produces oceans of log
messages we usually don't want.

In r1780246, I've finally changed debugging in gbuild to match how dmake
works: --enable-symbols and --enable-crashdump now also add debug symbols
to gbuild modules like they do to dmake modules, and the
--enable-symbols=small option is also implemented for GCC and Clang (sorry
Windows developers, MSVC doesn't seem to have it). The only extra benefit
of --enable-debug on top of this now, is that it disables compiler
optimizations - should we disable them for --enable-symbols too?

In r1780248 I've also made Java's .class files get full debugging info
whenever C++ does.

This should vastly improve running AOO under a debugger, as we get nice
line numbers and variable names for absolutely everything :-).

Damjan

Re: [lazy consensus] FreeBSD as a new supported platform?

[Dr. Michael Stehmann]

Am 24.01.2017 um 23:02 schrieb Andrea Pescetti:

> 
> I see some risk of confusion here. I mean, there is surely a set of
> "privileged" platforms that are those for which we build and make
> available releases from our download page: Windows, MacOS X, and Linux
> variants. Then there is a set of "semi-privileged" platforms where we as
> a project do not build releases, but that are aligned, submit patches
> upstream and so on (and these would be OS/2 and FreeBSD).
> 
> I don't know which group should be considered "supported" and I don't
> think that reading policy or sending tons of links would help much here.
> For sure if OS/2 is supported then FreeBSD is too. But if a user expects
> that "supported" means "available in binary form from the official site
> for this platform" then neither is supported.
> 
> Personally, I don't have a strong opinion on this and I would be in
> favor of adding FreeBSD to the "supported" list with the understanding
> that this doesn't automatically imply that we will build a FreeBSD
> release and make it available from the official site (we don't do that
> for OS/2 either).

Ok, we have two categories of "support" for platformes:

1. those, for which we build and make available releases

2. those, that are aligned, submit patches upstream and so on

IMO we should communicate these two categories of "support" clearly, so
the user knows very well, what "support" in his/hers case mean.

Kind regards
Michael




signature.asc
Description: OpenPGP digital signature

Re: Community building: give our User a chance to contribute!

[Jörg Schmidt]

 

> -Original Message-
> From: Simon Phipps [mailto:si...@webmink.com] 


> In fact Go-OO was started by Ximian in 2003, long before Novell bought
> them, as a convenient build system for developers not working 
> within Sun.
> The difficulty of getting the Sun team to accept patches, and the
> complexity of the Sun build system, meant that most 
> developers external to
> Sun used Go-OO as their repository.
> 
> There were indeed strong words spoken by many people 
> (including me on Sun's
> behalf) but for the most part Go-OO maintained its role as a 
> downstream
> convenience for non-Sun contributors and played a positive 
> role developing
> a developer community around the code. I think we would all 
> be well served
> by dropping the decade-old hostility to it at this point.

For me, the one who is working against OpenOffice, or members of the OpenOffice 
community offended, an opponent of OpenOffice.

I will never forgive what Michael Meeks said against OpenOffice! No way


Jörg


-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org