Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Messages - mackan

Pages: [1]
1

@mackan
my question is about the file system to use... Windows 10 uses NTFS, Linux uses FAT32 . I have no idea of how a file written in a file system can be copied into another file system, so my question is : "must you have the same file system on the compiling machine and on the executing machine? Or is the copy of the compiled file  a problem managed by the OS?
[/quote]

Standard for Linux is EXT4, I think, but no - it should not make a difference. What wine does is setting up a virtual environment, of sorts, and it can't really see beyond some fixed mount points. All the files (including the source) is kept in the same directory and the IDE sees the source code etc. There is no reason for the compiler / linker to be anything other than filesystem agnostic, right?


2
Thank you. I'll try that.

EDIT: Nope. Does not work. I am not sure, exactly, what does not work, though but it refuses to run under wine OR wine-console. Or rather - the IDE / Editor works fine. And it does the first step of the compilation. But then, when it should link the program (or - if QB64 is a pre-processor, compile the C-code) it crashes / hangs infinitely. Same behaviour regardless of I run 32 or 64 bit windows version in wine.

Ah, well.

3
here a suggest
https://en.wikipedia.org/wiki/Cross_compiler#GCC_and_cross_compilation
I imagine that using a cross compiler you must use a common shared file system to copy the final executable from original compiler machine to destination machine. Do you confirm this ?

I can use GCC as a cross-compiler, yes. That is not the problem. The problem is that I want to tell qb64 -c if it should compile to a native Linux binary or a Windows binary.

I am not sure I understand what you want me to confirm.

4
OK - I tried to run it under the wineconsole and it runs and makes the first pass of the compilation (qb64 -z) but then something hangs. Is there a way to dig out the files created by qb64 (.exe) and compile them, using another compiler / make my own make script?

I mean - qb64 is already using gcc as the compiler, so it must be possible to make a workaround somehow...

5
Hi!

As I understand it, the qb64 IDE / compiler pre-compiles to C, before (on Linux) compiling with gcc. Is there any way I can choose the compiler so that I can build windows binaries (.exe) with it? I know that GCC should be able to do this, but I don't seem to be able to pass any -m flags (-mwindows or -mconsole) to the gcc compiler from qb64 -c (or -x)

If it is not possible to either pass on compiler flags OR use different compilers (like mingw) - is there an installer of qb64 that can be installed under wine?

 

Pages: [1]