-
Notifications
You must be signed in to change notification settings - Fork 1.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
XMake - Build System #6169
Comments
Is there any guideline about how to build xmake in Windows? |
https://github.com/xmake-io/xmake/blob/master/.appveyor.yml |
new install script, install to ~/.local and add sh profile (recommended) https://xmake.io/#/guide/installation?id=installation make build
./scripts/get.sh __local__ __install_only__ old install script, install to /usr make build
./install installdir I'm not sure it support using mingw/make to build xmake on windows. Maybe we need modify some makefiles and code files to support it. Now we can only use xmake to build xmake or use nsis installation package to install it directly. You can open a issue in xmake/issues if compile errors on msys/mingw. I will attempt to support it. |
I will add core/plat/mingw in these days. |
I have improved xmake to compile it on mingw/msys. It has been compiled successfully on msys/mingw for xmake/dev branch. compile and install xmake: make build
make install prefix=/usr You can try it again. however, there are still some problems during operation, such as process execution. e.g. $ xmake l os.exec "echo hello"
1 [main] xmake 1887 dofork: child -1 - forked process 4512 died unexpectedly, retry 0, exit code 0xC0000135, errno 11
error: exec(echo hello) failed(-1)! I attempt to run |
@waruqi Hold your horses. What is your build environment? From your last message it seems you're building under MSYS2, but in your opening comment you asked as package under MINGW. Do not mix them up. The |
I have tested both the msys and mingw environments. ruki@DESKTOP-A6MFTOV MINGW64 ~
$ uname
MINGW64_NT-10.0-14393
ruki@DESKTOP-A6MFTOV MINGW64 ~
$ which xmake
/usr/bin/xmake
ruki@DESKTOP-A6MFTOV MINGW64 ~
$ xmake l os.exec "echo hello"
1 [main] xmake 1000 dofork: child -1 - forked process 4844 died unexpectedly, retry 0, exit code 0xC0000135, errno 11
error: exec(echo hello) failed(-1)! ruki@DESKTOP-A6MFTOV MSYS ~
$ uname
MSYS_NT-10.0-14393
ruki@DESKTOP-A6MFTOV MSYS ~
$ which xmake
/usr/bin/xmake
ruki@DESKTOP-A6MFTOV MSYS ~
$ xmake l os.exec "echo hello"
0 [main] xmake 1308 dofork: child -1 - forked process 1580 died unexpectedly, retry 0, exit code 0xC0000135, errno 11
error: exec(echo hello) failed(-1)! |
I have supported compiling xmake on msys/mingw and it worked very well. But we must use mingw-w64-[i686|x86_64]-gcc to compile xmake (dev branch). $ pacman -S mingw-w64-x86_64-gcc
$ which gcc
/mingw64/bin/gcc
$ cd xmake
$ make build
$ make install prefix=/usr run xmake to compile program: ruki@DESKTOP-A6MFTOV MINGW64 /tmp
$ xmake create test
create test ...
[+]: src\main.cpp
[+]: xmake.lua
[+]: .gitignore
create ok!
$ cd test
$ xmake
checking for the architecture ... x86_64
[ 0%]: compiling.release src\main.cpp
[100%]: linking.release test.exe Currently it is not supported to compile it with msys /gcc, because the generated xmake still has some running problems during the running process. And I alse improved the PKGBUILD, you can see |
@waruqi Like I said, do not mixup MSYS2 and MINGW. This line is wrong: Should be: MINGW binaries should NEVER go into |
Got it, thanks! @StarWolf3000 $ pacman -S mingw-w64-x86_64-gcc
$ which gcc
/mingw64/bin/gcc
$ cd xmake
$ make build
$ make install prefix=/mingw64 Or $ pacman -S mingw-w64-i686-gcc
$ which gcc
/mingw32/bin/gcc
$ cd xmake
$ make build
$ make install prefix=/mingw32 |
The linked PKGBUILD does not work in mingw-w64-x86_64 but the dev branch complied successfully. |
I haven’t published a new release version, the 2.2.9 version in PKGBUILD cannot be compiled. I only update PKGBUILD to use |
@Biswa96 I have published the release version (v2.3.1) and support mingw. |
@Biswa96 Did you use |
Both shows the error. |
I will look at it later. |
@Biswa96 It was because the pkg/bin directory was not created during running I have fixed this problem in the dev branch. But in the current version, you can temporarily modify PKGBUILD to solve this problem.
|
Some issues:
|
This is indeed a problem, I need to improve
/mingw64/bin/xmake.exe
It is just a legacy problem. core/makefile
|
@Biswa96 I have updated xmake-v2.3.1.tar.gz and imrpove You can update PKGBUILD and try it again.
|
|
I have fixed it, please update sha256 and redownload tar.gz to makepkg. sha256sums=('7aea3ccd4cdd80efad6825761fd75b2de5813a72e08e7fc4b7c4eb0671d6ff28') When run |
Ohh... forgot to check the 32bit build. The 32bit build failed. See the linked PR CI build. |
You can try If it still fails, I'll take a look tomorrow. |
I have fixed it on mingw32, you can update sha256 and try it again. b2e46d9b4dd48fb70d32a314ca4ba12d42b0b294f5e2179c5c09c56f9c52933b |
xmake have been merged. #6224 |
@waruqi Please close this. |
@StarWolf3000 I cannot close it. |
Why has xmake been merged and I executed pacman to update the database and still can't find it? $ pacman -Syu
mingw32 is up to date
mingw64 is up to date
msys is up to date
$ pacman -S mingw-w64-x86_64-xmake
error: target not found: mingw-w64-x86_64-xmake |
@StarWolf3000 Got it, thanks! |
@waruqi
output:
output: |
please open new issues in xmake/issues. you can only use the default platform on msys/mingw64 xmake f -c |
Would it be possible to join this build system in the package?
XMAKE_PKBUILD-ARCH
The text was updated successfully, but these errors were encountered: