Good day comrades coders, and coders linuksoidam doubly!
I'm interested in the next question:
What is the most effective way to collect code in exe-shnik?
This refers not only to the assembly with a given extension, but also to the performance in the Win axes. Both console, and programs with own interface.
How do you do it? If you do.
I do not have the opportunity to use a virtual machine or put Win.
What if you install, for example, VS or Delphi, run it with a wine, write to them using WinAPI libraries and, as a result, build, will the resulting file be usable under Windows?
If you recommend a cross-platform compiler, then throw a small HowTo or link to it please.



    5 answers 5

    What if you install, for example, VS or Delphi, run it with a wine, write to them using WinAPI libraries and, as a result, build, will the resulting file be usable under Windows?

    Yes it is possible. The resulting executable file will be the same as when building under Windows. The only caveat is related to the fact that VS and Delphi are serious software packages and their arbitrary version with an arbitrary version of wine and linux may simply be inoperable. But with rather old and 'mature' versions of the studios there will be no problems.

    What is the most effective way to collect code in exe-shnik?

    A compiler that supports cross-compilation. This means that the compiler will be under linux, and the output code will be under windows. Search Google for keywords gcc, cross-compile, windows. I also recommend paying attention to the Mingw32 and Cygwin projects: they allow you to write programs under windows using gcc, i.e. you can make portable programs between linux and windows environments with the same source code, by simple recompilation.

    • 2
      And thank you again - Tomagavk 8:50 pm

    Correct gecube says:

    I also recommend paying attention to the Mingw32 and Cygwin projects: they allow you to write programs under windows using gcc, i.e. you can make portable programs between linux and windows environments with the same source code, by simple recompilation.

    Here's how for C in my Geany the build parameters look like:
    Compile UNIX: gcc -lm -o "% e" "% f"
    Compile WIN: i586-mingw32msvc-gcc -o "% e" .exe "% f"
    Build: gcc -Wall -c "% f"

    Run: "./%e"
    Run EXE: "./%e".exe

      Or maybe try something like Java or interpreted languages ​​- Perl, Python, Ruby?

        Collected under the Wine exe will be. And so read about Lazarus (and FP); know how to cross-compile Mono, as well as about the GCC and its keys.

          Virtual machines are used in production; if the percent supports embedded virtualization, then set paralels, if not, then virtualbox. On an average computer, a client virtual machine with Windows or linux works quite fast; I work with C #.