On 10/17/2020 9:43 AM, Achim Gratz wrote:
Ken Brown writes:
There's no need for a new release at the moment, but I'm attaching the cygport
file I would use if there were. It differs in only very minor ways from the
current cygport file (also attached).
For your problem with the debuginfo that
Ken Brown writes:
> There's no need for a new release at the moment, but I'm attaching the
> cygport
> file I would use if there were. It differs in only very minor ways from the
> current cygport file (also attached).
For your problem with the debuginfo that we've briefly discussed on IRC:
I
> Am 11.11.2018 um 23:38 schrieb Ken Brown:
> > There's no need for a new release at the moment, but I'm attaching the
> > cygport
> > file I would use if there were. It differs in only very minor ways from the
> > current cygport file (also attached).
> >
> > I've tested that the upstream git re
> Am 11.11.2018 um 23:38 schrieb Ken Brown:
> > There's no need for a new release at the moment, but I'm attaching the
> > cygport
> > file I would use if there were. It differs in only very minor ways from the
> > current cygport file (also attached).
> >
> > I've tested that the upstream git re
Am 11.11.2018 um 23:38 schrieb Ken Brown:
There's no need for a new release at the moment, but I'm attaching the cygport
file I would use if there were. It differs in only very minor ways from the
current cygport file (also attached).
I've tested that the upstream git repo builds and passes all
>
> Hi.
>
> I contacted the doxygen maintainer, Warren Young, privately because I
> had encountered a bug [1] in doxygen 1.7.4. I knew that this bug was
> fixed in later versions of doxygen, and I asked if he could upload a
> more recent version. Warren replied and very kindly offered me the
On 9/29/2012 10:33 AM, David Stacey wrote:
Hi.
I contacted the doxygen maintainer, Warren Young, privately because I
had encountered a bug [1] in doxygen 1.7.4. I knew that this bug was
fixed in later versions of doxygen, and I asked if he could upload a
more recent version. Warren replied and
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Max Bowsher wrote:
| There is a copy of the libpng source code embedded in the doxygen source
| package. By default it builds a private copy of libpng and embeds it in
| the doxygen binaries. This seemed to me like needless duplication, so I
| made
Dave Korn wrote:
> Max Bowsher wrote on 02 May 2008 02:45:
>
>> Warren Young wrote:
>>> Dave Korn wrote:
requires: cygwin libpng12
The requires: line looks wrong to meWhy libpng?
>>> Ask Max. :)
>> Last time I looked there was a copy of libpng embedded in the doxygen
>> source
Warren Young wrote on 02 May 2008 00:10:
> I can't get graphviz to build cleanly under cygport yet.
Looks like you may not need to need to! Volker's sense of timing is
impeccable :)
cheers,
DaveK
--
Can't think of a witty .sigline today
Max Bowsher wrote on 02 May 2008 02:45:
> Warren Young wrote:
>> Dave Korn wrote:
>>> requires: cygwin libpng12
>>>
>>> The requires: line looks wrong to meWhy libpng?
>>
>> Ask Max. :)
>
> Last time I looked there was a copy of libpng embedded in the doxygen
> source tree. Building anoth
Warren Young wrote:
> Dave Korn wrote:
>> requires: cygwin libpng12
>>
>> The requires: line looks wrong to meWhy libpng?
>
> Ask Max. :)
Last time I looked there was a copy of libpng embedded in the doxygen
source tree. Building another copy seemed rather dumb when it's in the
distro as a
Dave Korn wrote:
requires: cygwin libpng12
The requires: line looks wrong to meWhy libpng?
Ask Max. :) It may have had to do with a historical ability to use
graphviz/dot or something like that. Max's latest doesn't do this, nor
does mine, because I can't get graphviz to build cleanl
Warren Young wrote on 01 May 2008 23:15:
> Taking over maintainership of this package from Max Bowsher. Ported
> build from g-b-s to cygport and updated from 1.5.1 to 1.5.5, so I'd like
> at least one GTG before I post the RFU message.
>
> http://etr-usa.com/cygwin/doxygen/setup.hint
sdesc: "A
14 matches
Mail list logo
