Who worked with sourceforge.net sources? In the lists of the source file are listed such as makefile.in ... how can you compile a similar source on Windows? As I understand it, apparently, similar sources are designed to work under Unix-systems, is this true? There are also two src folders - in it .h and .c files, and a man folder. How to be? Thank!

  • Compile an abstract program is unlikely to succeed. If the program is sharpened under Linux, then it may well be that compiling it might work out under Windows, but using it - only under Linux. - KoVadim
  • her exeshnik works fine on Windows, and I open the language files in the src folder, except that it is impossible to compile, the project itself is not ... - Pentium
  • Put * nix environment (for example Msys) on Windows and work. - avp
  • sourceforge.net/projects/hyenae/files/0.36-1 at this address lies the source code. help me figure it out, maybe I don’t understand something ... thank you! - Pentium
  • @Pentium, everything is written there, and you can watch on the spot without downloading. But what I do not understand, why do you need it? Matches for children is not a toy! - avp

1 answer 1

The phrase "no project itself" means the absence of a project file that you would open in your IDE (VisualStudio), right? The project file, roughly speaking, contains the information necessary for the integrated environment to work correctly with source code files, resources, forms, etc. You have included a new source file - an entry is added to the IDE project file. Based on the project file, the IDE generates a Makefile assembly file, executing the rules of which the make program calls the necessary utilities such as compilers, linkers, etc.

The build file (Makefile) can also be written manually, but it is often bulky. In the GNU world, autoconf / automake utilities are used to automate the generation of Makefiles. With their help, in particular, the Makefile.in template was created in the project under consideration, as well as the configure script (script).

The sequence of actions is as follows:

  1. Put MinGW / MSys or Cygwin (the first is better - less dependencies)
  2. Open MSys console
  3. Go to the previously unpacked project folder
  4. Run the configure script with the command ./configure
  5. If everything is in order, a Makefile will be built in the directory.
  6. Run make with the make command.
  7. If everything is in order, an executable .exe file will be built in the src directory
  8. Go to src, run .exe or run the command make install and it will be possible to run .exe from any directory in the MSys console.

In step 4, the configure script can start swearing at the absence of any capabilities of the compiler or third-party libraries (MSys contains a minimal set). You can try to look for source code dependencies and install as described above.

To run outside the MSys console, you will need some libraries (when you try to start, you will see a message about what is missing), for example, mingw-10.dll. They can be found in the wilds of the MinGW and MSys installation directories.

In any case, be patient and tambourine. Good luck.

  • Thanks a lot, I'll try now ... - Pentium