Missing mingw32-make

[Amno Jeeuw]

Following the install.txt file, after typing
cd %WXWIN%\build\msw
mingw32-make -f makefile.gcc

I get the following error:

if not exist gcc_mswud mkdir gcc_mswud
makefile.gcc:5089: recipe for target 'gcc_mswud' failed
if not exist ..\..\lib\gcc_lib mkdir ..\..\lib\gcc_lib
makefile.gcc:5639: recipe for target '..\..\lib\gcc_lib' failed

What can I do to fix this problem?

[Igor Korot]

Hi,

Did you install the compiler?

What happen if you type mingw32-make?

Thank you.

>
> --
> Please read http://www.wxwidgets.org/support/mlhowto.htm before posting.
>
> To unsubscribe, send email to wx-users+u...@googlegroups.com
> or visit http://groups.google.com/group/wx-users

[Vadim Zeitlin]

On Fri, 28 Jul 2017 07:14:58 -0700 (PDT) Amno Jeeuw wrote:

AJ> Following the install.txt file, after typing
AJ> cd %WXWIN%\build\msw
AJ> mingw32-make -f makefile.gcc
AJ>
AJ> I get the following error:
AJ>
AJ> if not exist gcc_mswud mkdir gcc_mswud
AJ> makefile.gcc:5089: recipe for target 'gcc_mswud' failed
AJ> if not exist ..\..\lib\gcc_lib mkdir ..\..\lib\gcc_lib
AJ> makefile.gcc:5639: recipe for target '..\..\lib\gcc_lib' failed
AJ>
AJ> What can I do to fix this problem?

Are you running this from DOS command prompt, i.e. cmd.exe and _not_ from
MSYS? Your SHELL environment variable should be set to cmd.exe, if defined
at all.

Also, what do you mean by "missing" mingw32-make when you apparently do
have it?

Regards,
VZ

--
TT-Solutions: wxWidgets consultancy and technical support
http://www.tt-solutions.com/

[Amno Jeeuw]

I am running it from the cmd.exe prompt.

[Vadim Zeitlin]

On Fri, 28 Jul 2017 17:34:57 -0700 (PDT) Amno Jeeuw wrote:

AJ> I am running it from the cmd.exe prompt.
AJ>
AJ> On Friday, 28 July 2017 10:14:59 UTC-4, Amno Jeeuw wrote:
AJ> >

AJ> > Following the install.txt file, after typing
AJ> > cd %WXWIN%\build\msw
AJ> > mingw32-make -f makefile.gcc
AJ> >

AJ> > I get the following error:
AJ> >
AJ> > if not exist gcc_mswud mkdir gcc_mswud
AJ> > makefile.gcc:5089: recipe for target 'gcc_mswud' failed
AJ> > if not exist ..\..\lib\gcc_lib mkdir ..\..\lib\gcc_lib
AJ> > makefile.gcc:5639: recipe for target '..\..\lib\gcc_lib' failed
AJ> >
AJ> > What can I do to fix this problem?

Sorry, no idea what the problem is then. If make really doesn't give any
other error message, you might try running it under Process Explorer and
monitor all its file system accesses to check which one results in an
error. It could be due to missing permissions, for example.

[Amno Jeeuw]

mingw32-make works, if I type 'mingw32-make --help' the help is displayed.

[Amno Jeeuw]

Running cmd.exe as an administrator [Run as administrator], I typed these commands:
===

cd %WXWIN%\build\msw
mingw32-make -f makefile.gcc

Which continues to fail, giving this error message:
===

if not exist gcc_mswud mkdir gcc_mswud
makefile.gcc:5089: recipe for target 'gcc_mswud' failed
if not exist ..\..\lib\gcc_lib mkdir ..\..\lib\gcc_lib
makefile.gcc:5639: recipe for target '..\..\lib\gcc_lib' failed
if not exist gcc_mswud mkdir gcc_mswud
makefile.gcc:5089: recipe for target 'gcc_mswud' failed
if not exist ..\..\lib\gcc_lib mkdir ..\..\lib\gcc_lib
makefile.gcc:5639: recipe for target '..\..\lib\gcc_lib' failed

Now, I realize that WxWidgets is a product that is mostly use in *nix OSs and that there are some projects that claim to use this toolkit, but how true is this claim and are the conditions under which this are developed 'using' WxWidgets?

Many people I have have talked to advice me not to use WxWidgets under Windows OS and others just wish me good luck. When asked why, they all say that WxWidgets does not compile under Windows and/or that WxWidgets was not designed to work properly under any OS than *nix OSs.

Is this true?

If there are any Windows 7+ users here, please let me know your opinion on this.

Thanks all for the help.

To unsubscribe, send email to wx-users+unsubscribe@googlegroups.com
or visit http://groups.google.com/group/wx-users

--

Sent from Microsoft Windows 10

[Igor Korot]

Hi,

This is complete bogus.
wxWidgets can be successfully compiled under all 3 major platforms: Windows,
*nix and OSX.
And it can successfully be used to develop a real-life applications under them.

What is the complete path under which you installed wxWidgets? Do you
have the proper
rights there? Can you try to do this:

[code]
cd %WXWIN%\build\msw

mkdir ..\..\lib\gcc_lib

[/code]

Also, out of curiosity - where did you get you compiler? What version is it?

Thank you.

> Sent from Microsoft Windows 10
>

[Steve Barnes]

On 30/07/2017 12:56, Amno Jeeuw wrote:
<Snip>

>
> Now, I realize that WxWidgets is a product that is mostly use in *nix
> OSs and that there are some projects that claim to use this toolkit, but
> how true is this claim and are the conditions under which this are
> developed 'using' WxWidgets?
>
> Many people I have have talked to advice me not to use WxWidgets under
> Windows OS and others just wish me good luck. When asked why, they all
> say that WxWidgets does not compile under Windows and/or that WxWidgets
> was not designed to work properly under any OS than *nix OSs.
>
> Is this true?
> If there are any Windows 7+ users here, please let me know your opinion
> on this.
>
> Thanks all for the help.
>

I have been, and still am, using wxWidgets and wxPython under Windows
from 3.11 through XP, NT, 7, 8 & 10, as well as *nix, on multiple
projects with multiple companies. These projects have included
deliverable solutions for Sonar use, (both real-time and back office
analysis), various hardware control and diagnostic packages, test and
analysis suites, document control and analysis, etc. - I have been able
to build the tool chain with gcc and a number of versions of MS C++.

So I can say that the above is absolute rubbish!

Just make sure that you have one of the supported tool chains for your
platform, (preferably with a CLEAN install of the same), and all of the
dependencies, prerequisites, etc. & follow the instructions at one of:
https://wiki.wxwidgets.org/Compiling_wxWidgets_with_MinGW or
https://wiki.wxwidgets.org/Compiling_WxWidgets_with_MSVC_(2) depending
on your tool chain.

You could also consider downloading one of the pre-built windows
libraries from http://wxwidgets.org/downloads/, see and
https://ci.appveyor.com/project/wxWidgets/wxwidgets for statistics such as:
Fix compilation with wxUSE_ACCEL==0
1956
5 hours ago by Artur Wieczorek
master d57672ee
4 hours ago in 42 min 47 sec
JOBS
JOB NAME TESTS DURATION
Environment: TOOLSET=msbuild, CONFIGURATION=DLL Release, ARCH=x64,
wxUSE_STL=1
4 min 11 sec
Environment: TOOLSET=nmake, VS=9.0, BUILD=release, ARCH=x86, wxUSE_STL=0
4 min 27 sec
Environment: TOOLSET=nmake, VS=14.0, BUILD=debug, ARCH=amd64, wxUSE_STL=1
3 min 48 sec
Environment: TOOLSET=mingw, wxUSE_STL=0
9 min 14 sec
Environment: TOOLSET=msys2, MSYSTEM=MINGW32
9 min 22 sec
Environment: TOOLSET=cygwin

All of the above builds succeeded.

--
Steve (Gadget) Barnes
Any opinions in this message are my personal opinions and do not reflect
those of my employer.

---
This email has been checked for viruses by AVG.
http://www.avg.com

[John Ralls]

> On Jul 30, 2017, at 12:56 PM, Amno Jeeuw <amno...@gmail.com> wrote:
>
> Running cmd.exe as an administrator [Run as administrator], I typed these commands:
> ===
> cd %WXWIN%\build\msw
> mingw32-make -f makefile.gcc
>
> Which continues to fail, giving this error message:
> ===
> if not exist gcc_mswud mkdir gcc_mswud
> makefile.gcc:5089: recipe for target 'gcc_mswud' failed
> if not exist ..\..\lib\gcc_lib mkdir ..\..\lib\gcc_lib
> makefile.gcc:5639: recipe for target '..\..\lib\gcc_lib' failed
> if not exist gcc_mswud mkdir gcc_mswud
> makefile.gcc:5089: recipe for target 'gcc_mswud' failed
> if not exist ..\..\lib\gcc_lib mkdir ..\..\lib\gcc_lib
> makefile.gcc:5639: recipe for target '..\..\lib\gcc_lib' failed
>
> Now, I realize that WxWidgets is a product that is mostly use in *nix OSs and that there are some projects that claim to use this toolkit, but how true is this claim and are the conditions under which this are developed 'using' WxWidgets?
>
> Many people I have have talked to advice me not to use WxWidgets under Windows OS and others just wish me good luck. When asked why, they all say that WxWidgets does not compile under Windows and/or that WxWidgets was not designed to work properly under any OS than *nix OSs.
>
> Is this true?
> If there are any Windows 7+ users here, please let me know your opinion on this.
>

You can't build with mingw from cmd.exe. You mist use one of the shells provided by mingw. You'll find them in the Start menu under either MSYS or MSYS2 depending on which flavor of mingw you're using.

Regards,
John Ralls

[Gunter Königsmann]

The only time compiling did not work for me was when mingw wasn't in the search path of my system and therefore could not be found. Which wasn't a wxWidgets problem and was easy to correct.

[Vadim Zeitlin]

On Sun, 30 Jul 2017 07:56:32 -0400 Amno Jeeuw wrote:

AJ> Running cmd.exe as an administrator [Run as administrator], I typed these
AJ> commands:
AJ> ===

AJ> cd %WXWIN%\build\msw
AJ> mingw32-make -f makefile.gcc
AJ>

AJ> Which continues to fail, giving this error message:
AJ> ===
AJ> if not exist gcc_mswud mkdir gcc_mswud
AJ> makefile.gcc:5089: recipe for target 'gcc_mswud' failed

Have you checked your SHELL environment variable or tried to debug the
issue as I advised in a previous message using Process Explorer? The
problem must be really trivial, but it's very hard to guess what it is
without having more information.

AJ> Now, I realize that WxWidgets is a product that is mostly use in *nix OSs

Not that it changes anything, but this is completely false, of course,
majority of wx users are under MSW.

AJ> Many people I have have talked to advice me not to use WxWidgets under
AJ> Windows OS and others just wish me good luck. When asked why, they all say
AJ> that WxWidgets does not compile under Windows and/or that WxWidgets was not
AJ> designed to work properly under any OS than *nix OSs.
AJ>
AJ> Is this true?

Obviously not. I guess you're just trying asking rhetorical questions in
order to solicit more responses, but in case you're not, you can be sure
that these "many people" have absolutely no idea about what they're
talking.

AJ> If there are any Windows 7+ users here, please let me know your opinion on
AJ> this.

There are, at conservative estimate, tens of thousands of wx users under
Windows (only a small part of which is subscribed to this list, of course).
I'm sorry we can't help you with your particular problem, but you really
need to spend some time on debugging it instead of just assuming that it
doesn't work, which is obviously false.

[Bob Paddock]

His error looks very similar to the one I get when trying to build the
Minimal Sample
from wx 310 under Windows 7 or Windows 10 from a cmd box.

It is the mkdir command that is failing. If you create gcc_mswud by
hand things build fine.
which mkdir.exe shows bash\bin\mkdir.exe which is probably not the one
the build system expected to run from the cmd box.

This is of course an issue with my paths and not the fault of WX.
So it is the paths on his system that need addressed.

Using GCC 7.1.0 from https://nuwen.net/mingw.html ,
running make -fmakefile.gcc in samples/minimal gives this:


[G104]J:\WX\310\samples\minimal>make -f makefile.gcc
OBJS=gcc_mswud

if not exist gcc_mswud mkdir gcc_mswud

process_begin: CreateProcess(NULL, J:/Apps/MinGW150/bin/ -c "if not
exist gcc_mswud mkdir gcc_mswud", ...) failed.
make (e=5): Access is denied.
make: *** [makefile.gcc:210: gcc_mswud] Error 5

make in this case is really mingw32-make from the Nuwen package.

[Amno Jeeuw]

Yes Igor, I appreciate your input.

It is easy to say, the sky is blue, but is not easy to provide blind people with what is necessary for them to see the blue sky.
I am not here to have arguments about who has be biggest... shoes. All I want is for someone here to tell me why WxWidgets *fails* to compile, when I am following the documentation provided by the toolkit.
Now, I stand by my statement and my concerns about WxWidgets, because I have not seen any changes since the first time I tried to compile the toolkit; saying otherwise is just noise.
Let's talk about what is at hand and answer the why and the how.

Thanks.

[Igor Korot]

Hi,

On Thu, Aug 10, 2017 at 7:37 AM, Amno Jeeuw <amno...@gmail.com> wrote:
> Yes Igor, I appreciate your input.
>
> It is easy to say, the sky is blue, but is not easy to provide blind people
> with what is necessary for them to see the blue sky.

Are you talking about legally blind, color blind or some other blind people? ;-)
But I think we are going politics here which is OT in this ML.

> I am not here to have arguments about who has be biggest... shoes. All I
> want is for someone here to tell me why WxWidgets *fails* to compile, when I
> am following the documentation provided by the toolkit.
> Now, I stand by my statement and my concerns about WxWidgets, because I have
> not seen any changes since the first time I tried to compile the toolkit;
> saying otherwise is just noise.
> Let's talk about what is at hand and answer the why and the how.

As Vadim said - try building the library from the MinGW Terminal and the Windows
Command Prompt one.

If it still fails with the same issue then we can talk more.

Thank you.

[Eduardo Luis Marcovecchio]

Hello guys, this is my first post here.

Amno, I would like to know which are those problems wxWidgets have on Windows. I confess I had a hard time getting it to compile under Windows for the first time, each version needed a little tweak, in wxWidgets or in the compiler, but it definately works, for sure., And once compiled, is almost rock solid. I never used it under Linux, but my experiences on Linux are exactly the ones where things seem not to work out of the box, needing lots of tweaking.

One thing I would like to suggest: if you are using MingW, download TDM GCC and use it instead (http://tdm-gcc.tdragon.net/). I had better luck this way. If it doesn't work, try an older version. Sometimes it's just a matter of matching the correct compiler / wxWidgets / libs to make it work, or researching about erros messages and changing some command line option in the makefile.

It's the same process for any C/C++ library you may try to use in any platform.

What versions are you using for wx and compiler?

Hope it helps!

Eduardo

[Bob Paddock]

On Fri, Jul 28, 2017 at 10:14 AM, Amno Jeeuw <amno...@gmail.com> wrote:

> Following the install.txt file, after typing
> cd %WXWIN%\build\msw
> mingw32-make -f makefile.gcc

Make sure you have a clean path to the compiler and tools.

In the cmd box or MinGW terminal force the path to point only to the
compiler /bin directory.
On my system this would be done by doing this at the prompt:

PATH=J:\Apps\MinGW150\bin
Adjust yours accordingly.

On my system I get errors similar to yours due to my default path configuration.

How did you install MinGW and from where?