From: djd <dj...@cm...> - 2012-03-05 09:52:02
|
On 5/03/2012 6:32 PM, Sergio NNX wrote: > > Well, you already know the answer to that, since you were in exactly > > this position, and saw what happens ;-) > > > > > Your guess was incorrect, but clouded by the issue that libregex.a is > > > just a copy of libgnurx.dll.a. > > > Do you still want the -v output? > > > > No. I guess you'll need to get the sources of that mingw-libgnurx > > package and build the static library yourself, to solve this. > > Ciao. > > We seem to be going around in circles here. Is it possible to have > access to this app source code so I can have a go at it? > > Cheers. > > > Yes, we have gone around a complete circle and I am back to more or less where this part started, the need for a `genuine' static libregex.a - except I did not realise it was not `genuine'. However, I am not complaining, the only c program I have ever compiled previously, maybe 30 years ago, was "Hello word" and I have never used mingw or gcc. I have learnt a lot through this exercise. I have attached two files, the original source uni2ascii.zip (its on the internet somewhere) and my modified version. Originally I tried using the configure script included in uni2ascii.zip, however after much trying, it was just too convoluted (for me) to easily work out what was going on, so I went back to the original *.c files and started again. That meant obtaining some additional source (getline, win32-uname, ...) and headers and I temporarily renamed the output convert.exe to avoid confusing myself. All these *.c files are in convert.zip and most of the extra headers plus the compile line I have been using. But some of the additional headers are in their usual directories and I cannot immediately remember what they were. However if they are not obvious to you, I am sure I can work it out. And thanks to Eli Zaretskii for his knowledge and doggedness in sticking with me when I must have appeared appallingly clueless to him. Regards |