#135 make and mingw32-make difference

Non_standard_use
closed
nobody
MSYS (18)
5
2011-08-11
2011-08-11
No

Being a new mingw32 & msys user I was unaware of the difference between the native make and mingw32's version leading to a bit of an issue.

Request: When using the native make command a warning stating something like "if errors occur try mingw32-make instead". A message like this should provide new users like myself a starting point to get their code compiling with msys and mingw32.

Discussion

  • Earnie Boyd

    Earnie Boyd - 2011-08-11
    • labels: 380073 --> MSYS
    • milestone: 102881 -->
     
  • Earnie Boyd

    Earnie Boyd - 2011-08-11
    • milestone: --> Non_standard_use
    • status: open --> closed
     
  • Earnie Boyd

    Earnie Boyd - 2011-08-11

    I suppose reading MSYS documentation didn't help? You should never use mingw32-make within MSYS, it just doesn't work. The original MSYS release had a post-install that renamed a program named make if it found one on PATH. Plans for POST-INSTALL scripting in mingw-get are in the works but will be a long time in the future.

    If the application is to be used by other systems such as Linux then the Makefile should be constructed using autoconf to avoid platform issues. MSYS original goal was to allow ./configure && make to occur for the mingw build system.

    Any errors coming from the make application are relative to the upstream GNU make application and is maintained there.

     
  • Keith Marshall

    Keith Marshall - 2011-08-12

    > Plans for POST-INSTALL scripting in mingw-get are in the works
    > but will be a long time in the future.

    Maybe not such a long time; I already have a rudimentary working implementation for PRE-INSTALL, POST-INSTALL, PRE-REMOVE, and POST-REMOVE :)

    There are some libmingwex.a issues I need to address before I publicise it, but discussion of those doesn't belong on this ticket.

     

Log in to post a comment.

Get latest updates about Open Source Projects, Conferences and News.

Sign up for the SourceForge newsletter:

JavaScript is required for this form.





No, thanks