Hi @List,
Are there DirectX 8 Headers avaiable?
Greetings, Peter
--
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and how IT managers can
piling extensions which use OpenMP and
> distributing them without the DLLs they depend on.
>
> These days I use my own toolchain builds, but in the past I have used
> Ozhan's ('sezero') builds of gcc pre-4.5.4. He supplies pthreads-w32
> (as far as I recall you needed
Hi William,
Am 03.01.2012 18:53, schrieb r...@libertysurf.fr:
> Dear both lists,
> I would like to understand better what is the difference between your two
> projects, in term of cross-compilation capabilities (linux -> windows).
> mingw-64 seems to be a much bigger project, but has not factual
Hi @All
First: Happy New Year!
In the last months i was developing a Cross Compiler Program (MinGW
32-Bit and Visual C/C++ 64-Bit).
I choosed QT 4.7 - but: The MS Compiler only supports OpenMP 2.0 so the
Code was not much efficient,
mostly parallel for loops. The Problem at MinGW 4.5 was, thadt
Sorry if you feel angry and not all person in the world having the same
views like
you. There is no Problem and nothing needs to solve - what you talking
about?
Am 30.12.2011 11:57, schrieb JonY:
On 12/30/2011 18:14, Peter Meyer wrote:
Am 30.12.2011 10:06, schrieb JonY:
You should be
Am 30.12.2011 10:06, schrieb JonY:
> You should be recompiling GTK for win32 also, you can't use native
> libraries when cross compiling. You may also want to build a specially
> modified pkg-config for cross compiles, eg i686-w64-mingw32-pkg-config
> that points to your special PKG_CONFIG_PATH for
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;
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
> /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
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
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
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
Hi,
Iam Peter from the Centauri Project here at Sourceforge and we are also
OpenSource (unfortently, iam alone on the Project right now but this
is an diffrent story).
I hope some one can point me to the right point:
I just downloaded Sezeros
"mingw-w64-bin_x86_64-mingw_2001_sezero.zip" fro
14 matches
Mail list logo
