On 29 December 2011 19:27, Chris Sutcliffe wrote:
> Using the latest update to the mingw-w64 packages in Cygwin, I've run
> in to an issue where swprintf is truncating an included string.
The issue is with the new __mingw_*printf functions that were added.
Using this code:
#include
#include
in
Hi All,
Using the latest update to the mingw-w64 packages in Cygwin, I've run
in to an issue where swprintf is truncating an included string. In my
code i have:
wcscpy(method, TEXT("Logoff"));
swprintf(messageText, TEXT("Are you sure you want to %s?"), method);
which results in "Are you sure yo
JonY:
> You should be cross compiling for windows, you don't need X11 or any
> Cygwin GTK DLLs. If you do, you're doing it wrong somewhere.
Can you explain this a bit more precise?
if you compile this Program base.c
#include
int main( int argc, char *argv[] )
{
GtkWidget *window;
On 12/30/2011 05:07, Peter Meyer wrote:
> Hi again,
>
> After ours of trial and error i will give some feedback and share my
> results (maybe it is usefull for
> anyone out there, finding this on the list archiv via Google (Date of
> writing is: 12/29/2011).
>
> Ok, Cygwin 1.7.x worked at compi
Hi again,
After ours of trial and error i will give some feedback and share my
results (maybe it is usefull for
anyone out there, finding this on the list archiv via Google (Date of
writing is: 12/29/2011).
Ok, Cygwin 1.7.x worked at compilation level, but if you wish to run the
GTK Gnome2 App
29.12.2011 16:59, schrieb JonY:
> autotools has config.log. Automated buildsystems are still more
> convenient than those that require special attention on every
> different platform. Using custom makefiles will only make it worst,
> since you now have a dozen other authors with their own handcr
On 12/29/2011 22:42, Peter Meyer wrote:
>> /off topic rant
>>
>> Most custom Makefiles cannot handle systems that are different from the
>> developer's, requiring manual editing to fix it. This gets very tedious
>> when you keep running into them over and over.
>
> Thadt are the problems you have
> /off topic rant
>
> Most custom Makefiles cannot handle systems that are different from the
> developer's, requiring manual editing to fix it. This gets very tedious
> when you keep running into them over and over.
Thadt are the problems you have to deal with it, but thadts no Problem,
if you a
On 12/29/2011 19:51, Peter Meyer wrote:
> Hi
>
> Am 29.12.2011 10:30, schrieb JonY:
>> Oh boy, looks like you skipped some manuals.
>
> Thadt might be true, but i allways struggle to find the correct manuals.
> I Google all the time but it is verry
> hard for me to find the hardfacts. Of cause,
Hmm, indeed strange. I subscribed you via adminstrative tool now.
Regards,
Kai
--
Ridiculously easy VDI. With Citrix VDI-in-a-Box, you don't need a complex
infrastructure or vast IT resources to deliver seamless, secure
Hi Kai,
Hmm thadts sounds strange, because i have subscribed the Mailinglist and
in my Inbox was the Welcome message:
Welcome to themingw-w64-pub...@lists.sourceforge.net mailing list!
To post to this list, send your email to:
mingw-w64-public@lists.sourceforge.net
General information a
Hi Peter,
if you want that your replies getting unmanaged to this ML, then I
kindly ask you to subscribe to ML. Otherwise it might happen, that
your mails getting stuck there for some time, before a ML-manager
manually approves them.
You can subscribe to the ML via the link provided at
http://so
Hi
Am 29.12.2011 10:30, schrieb JonY:
> Oh boy, looks like you skipped some manuals.
Thadt might be true, but i allways struggle to find the correct manuals.
I Google all the time but it is verry
hard for me to find the hardfacts. Of cause, there are lots of
Informations out there, but if you
On 12/29/2011 07:17, Peter Meyer wrote:
> Hi (and thx for the reply)
>
> Am 28.12.2011 23:50, schrieb JonY:
>> LDFLAGS is very much autotools specific (avoid custom Makefiles if
>> possible). Your custom Makefile might not respect LDFLAGS env var. You
>> need to dive in and understand it before
Hi (and thx for the reply)
Am 28.12.2011 23:50, schrieb JonY:
> LDFLAGS is very much autotools specific (avoid custom Makefiles if
> possible). Your custom Makefile might not respect LDFLAGS env var. You
> need to dive in and understand it before being able to edit it
> correctly. I'm guessing
I have had to #ifdef all my printf code in 50+ programs because of this problem.
will this be fixed in mingw as well?
-
Jim Michaels
jmich...@yahoo.com
j...@jimscomputerrepairandwebdesign.com
http://JimsComputerRepairandWebDesign.com
http://JesusnJim.com (my personal site, has softwa
16 matches
Mail list logo
