On 8/25/2010 12:19 AM, JonY wrote:
since cygport and gcc has been updated, I can do the packaging without
any local hacks.
Here are the packages.
Overall comments: I see you reverted to bundling the DLLs with the
compiler packages (e.g. no separate mingw64-x86_64-libfoo-* tarballs).
While
Hi,
Mscgen is a message sequence chart rendering tool. It can be used
standalone or with Doxygen to help document call flows and is licensed
under the GPL. It's already packaged with Ubuntu:
http://packages.ubuntu.com/maverick/mscgen
http://packages.ubuntu.com/lucid/mscgen
Mscgen
Originally posted in
http://cygwin.com/ml/cygwin-apps/2010-08/msg00213.html
but I figure it needs its own thread.
When testing JonY's mingw64 compiler, I found that often the include
files ended up in the wrong directory. Also, JonY apparently did as
well, since his cygport(5)'s
On 9/1/2010 03:32, Charles Wilson wrote:
On 8/25/2010 12:19 AM, JonY wrote:
since cygport and gcc has been updated, I can do the packaging without
any local hacks.
Here are the packages.
Overall comments: I see you reverted to bundling the DLLs with the
compiler packages (e.g. no separate
On 8/31/2010 8:52 PM, JonY wrote:
On 9/1/2010 03:32, Charles Wilson wrote:
Rebuilds fine from source (*), but the binary tarball above is not ok.
It has the headers in the following directory:
usr/x86_64-w64-mingw32/sys-root/mingw/x86_64-w64-mingw32/include/
instead of
On 9/1/2010 10:28, Charles Wilson wrote:
On 8/31/2010 8:52 PM, JonY wrote:
On 9/1/2010 03:32, Charles Wilson wrote:
Rebuilds fine from source (*), but the binary tarball above is not ok.
It has the headers in the following directory:
On Tue, 2010-08-31 at 17:34 -0400, Charles Wilson wrote:
When testing JonY's mingw64 compiler, I found that often the include
files ended up in the wrong directory.
Often?
Also, JonY apparently did as well, since his cygport(5)'s
Which were likely borrowed from mine...
included this bit
