Native win32 build under cygwin fails

[GoogleCodeExporter]

What steps will reproduce the problem?
1.open cygwin
2.run ./autogen.sh
3.run ./configure CFLAGS=-mno-cygwin as described in the README

What is the expected output? What do you see instead?
configure fails:
./configure: line 4318: syntax error near unexpected token `GDLIB,'
./configure: line 4318: `     PKG_CHECK_MODULES(GDLIB, gdlib)'

What version of the product are you using? On what operating system?
Windows Vista Enterprise 32 bit, SP 2
Cygwin DLL 1.7.6-1

Please provide any additional information below, including sample input
file:
All required packages are installed as described in README.

Original issue reported on code.google.com by fthe...@grundfos.com on 24 Aug 2010 at 6:44

[GoogleCodeExporter]

I think this is because you don't have pkg-config installed under cygwin.

Can you run the cygwin setup.exe and check pkg-config is there and report back?

If that's it, I'll update the README.

Original comment by Michael....@gmail.com on 24 Aug 2010 at 8:41

• Changed state: Started

[GoogleCodeExporter]

OK, thanks for this hint. But the next problem occurred when running ./config:

---
checking for GDLIB... configure: error: Package requirements (gdlib) were not me
t:

No package 'gdlib' found

Consider adjusting the PKG_CONFIG_PATH environment variable if you
installed software in a non-standard prefix.

Alternatively, you may set the environment variables GDLIB_CFLAGS
and GDLIB_LIBS to avoid the need to call pkg-config.
See the pkg-config man page for more details.
---

gdlib is already installed in cygwin, so what may be the problem?
Thanks for your help, mscgen is such a great tool!

Original comment by fthe...@grundfos.com on 25 Aug 2010 at 6:38

[GoogleCodeExporter]

Hi again Michael,

I solved the problem by running the supplied bash-script 
<mscgen-trunk>/packaging/manual/win32.sh.

Finally, this is what I did to build a native win32 executable out of the 
current trunk:

1. install the prerequisites as described in the README
2. additionally install pkg-config
3. run ./win32.sh in <mscgen-trunk>/packaging/manual

After the build, the executable can be found in 
<mscgen-trunk>\mscgen-0.18\_build\src.

Maybe you can add these hints to the README.

Original comment by fthe...@grundfos.com on 25 Aug 2010 at 8:01

[GoogleCodeExporter]

I'm glad you got it going.

In the meantime I tried to build on Cygwin & Win32 and found similar problems 
from a fresh install.  gdlib doesn't have pkg-config stuff under Cygwin and so 
at r119 I've changed some things in the configure script and I think it should 
work much better.

I also took the line from the win32.sh build script and updated the README - 
hopefully the 0.18 release will be better now, or you could checkout trunk if 
you have the time.

Eitherway - thanks for bringing this to my attention.

Original comment by Michael....@gmail.com on 26 Aug 2010 at 12:13

• Changed state: Fixed

[GoogleCodeExporter]

Hi again,

as suggested, I updated my trunk, but now there are other problems.
I followed your instructions in README, but ./configure stops again:

./configure CFLAGS=-mno-cygwin GDLIB_CFLAGS="-I../gdwin32/include" GDLIB_LIBS 
="-L../gdwin32/lib -lbgd"
...
checking for gdlib-config... no
checking for pkg-config... /usr/bin/pkg-config
checking pkg-config is at least version 0.9.0... yes
checking for GDLIB... yes
checking for library containing gdImageColorAllocate... no
configure: error: Failed to find library containing gd

I attached a .zip file containing "config.log" and "configure", maybe it helps 
you to track down the problem.

Original comment by fthe...@grundfos.com on 26 Aug 2010 at 1:08

Attachments:

• config_files.zip

[GoogleCodeExporter]

Many thanks for rechecking and sending the output.  

I will look at this again.  I wonder if this is a difference in autoconfig 
versions we are using, as the passed flags don't look to have been effective 
for some reason.

Original comment by Michael....@gmail.com on 27 Aug 2010 at 8:53

• Changed state: Started

[GoogleCodeExporter]

Cool - I've reproduced this by changing the cygwin packages I've got installed 
(which shouldn't actually matter when specifying the command line switches!)

Original comment by Michael....@gmail.com on 6 Sep 2010 at 7:38

[GoogleCodeExporter]

I found quite a few bugs in the way configure was working on w32, although with 
the right Cygwin packages it would correctly build a win32 native binary.

r133 should fix these, and it's also given me a chance to fix up some aspects 
of FreeType detection too.

I'm marking this fixed as I think it should be okay now.

Original comment by Michael....@gmail.com on 7 Sep 2010 at 4:48

• Changed state: Fixed