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.
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,
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;
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
The goal is to move away from dmake. I do struggle with your point of
view, saying moving away from dmake is unimportant, and should be stopped.
I disagree with this position.
Am 16.04.20 um 23:04 schrieb Patricia Shanahan:
On 4/15/2020 10:08 AM, Damjan Jovanovic wrote:
On Wed, Apr 15,
On 4/15/2020 10:08 AM, Damjan Jovanovic wrote:
On Wed, Apr 15, 2020 at 3:15 PM Jim Jagielski wrote:
On Apr 15, 2020, at 3:01 AM, Damjan Jovanovic wrote:
We are also thin on new contributors, and I recall you saying they're
largely scared off by the current build system.
Two
On 4/14/20 9:46 PM, Peter Kovacs wrote:
If one wants to tap in our build system he needs to understand Perl,
shell, make, ant, XML, configure, ...
This is just way to complicated, especially if you want to bring in an
IDE to ease code development.
Damjan is not very happy with the
On Wed, Apr 15, 2020 at 3:15 PM Jim Jagielski wrote:
>
>
> > On Apr 15, 2020, at 3:01 AM, Damjan Jovanovic wrote:
> >
> >
> > We are also thin on new contributors, and I recall you saying they're
> > largely scared off by the current build system.
> >
>
> Two points:
>
> 1. I doubt that by
> On Apr 15, 2020, at 3:01 AM, Damjan Jovanovic wrote:
>
>
> We are also thin on new contributors, and I recall you saying they're
> largely scared off by the current build system.
>
Two points:
1. I doubt that by the time we finish porting to a whole new build system, we
will even
Hi All,
Damjan, thanks for providing the feature list on SCONs. I did not have
that on the able.
For me it is a promising Idea with a lot of questions attached to it.
And I am not 100% convinced it can solve the Issues where we got stuck
on Gmake.
I would also like to know which
On Wed, Apr 15, 2020 at 6:46 AM Peter Kovacs wrote:
> If one wants to tap in our build system he needs to understand Perl,
> shell, make, ant, XML, configure, ...
>
> This is just way to complicated, especially if you want to bring in an
> IDE to ease code development.
>
>
> Damjan is not very
Without knowing enough about the merits of the different build systems
we got where we are through a history in which a new build system is
selected every N years, but it takes more than N years to fully switch.
My recommendation is to pick one of the existing build systems, and get
If one wants to tap in our build system he needs to understand Perl,
shell, make, ant, XML, configure, ...
This is just way to complicated, especially if you want to bring in an
IDE to ease code development.
Damjan is not very happy with the features gmake offers. I am not sure
where
13 matches
Mail list logo
