This list is closed, nobody may subscribe to it.
2014 |
Jan
|
Feb
|
Mar
(6) |
Apr
(57) |
May
(43) |
Jun
(24) |
Jul
(21) |
Aug
(70) |
Sep
(112) |
Oct
(107) |
Nov
(150) |
Dec
(23) |
---|---|---|---|---|---|---|---|---|---|---|---|---|
2015 |
Jan
(35) |
Feb
(58) |
Mar
(64) |
Apr
(131) |
May
(71) |
Jun
(31) |
Jul
(29) |
Aug
(30) |
Sep
(22) |
Oct
(13) |
Nov
(46) |
Dec
(22) |
2016 |
Jan
(29) |
Feb
(49) |
Mar
(79) |
Apr
(67) |
May
(14) |
Jun
(5) |
Jul
(40) |
Aug
(31) |
Sep
(23) |
Oct
(34) |
Nov
(38) |
Dec
(28) |
2017 |
Jan
(36) |
Feb
(61) |
Mar
(18) |
Apr
(37) |
May
(25) |
Jun
(65) |
Jul
(20) |
Aug
(41) |
Sep
(17) |
Oct
(21) |
Nov
(29) |
Dec
(10) |
2018 |
Jan
(1) |
Feb
(8) |
Mar
|
Apr
(9) |
May
(5) |
Jun
(4) |
Jul
(5) |
Aug
(10) |
Sep
(12) |
Oct
(7) |
Nov
|
Dec
(3) |
2019 |
Jan
(16) |
Feb
(3) |
Mar
(33) |
Apr
(2) |
May
(17) |
Jun
(10) |
Jul
|
Aug
(3) |
Sep
(2) |
Oct
|
Nov
(6) |
Dec
(19) |
2020 |
Jan
(6) |
Feb
(8) |
Mar
(6) |
Apr
(17) |
May
(8) |
Jun
(12) |
Jul
(13) |
Aug
(3) |
Sep
(3) |
Oct
(1) |
Nov
(9) |
Dec
|
2021 |
Jan
(1) |
Feb
(8) |
Mar
(7) |
Apr
|
May
(8) |
Jun
(2) |
Jul
(2) |
Aug
(3) |
Sep
|
Oct
|
Nov
|
Dec
|
From: Ray D. <min...@gm...> - 2014-05-16 20:46:02
|
You can make your own versions of the PKGBUILD files for those projects. Do you know how to build one yourself yet? Enter makepkg-mingw basically.. I would recommend you compare the difference between qt5 and qt5-static for example to get an idea of the differences. Generally we are happy to provide both static and shared libraries for packages though, but sometimes there can be conflicts when doing this. E.g. packages that use .a extension for both static libraries and import libraries instead of .dll.a for the import library. Patches to fix support for co-existence are welcome too. On May 16, 2014 8:54 PM, "Jon bae" <jon...@gm...> wrote: > Hello everybody, > is it possible to get from this libs static versions? > openjpeg > fontconfig > gnutls > > I can compile them self static, but they are also in the mingw-packages, > so maybe it not so complicate to build them for both ways. I never have > done a pkg-packages, but when you need help for this libs I can try to > do it. > > Best Regards! > > Jonathan > > > > > ------------------------------------------------------------------------------ > "Accelerate Dev Cycles with Automated Cross-Browser Testing - For FREE > Instantly run your Selenium tests across 300+ browser/OS combos. > Get unparalleled scalability from the best Selenium testing platform > available > Simple to use. Nothing to install. Get started now for free." > http://p.sf.net/sfu/SauceLabs > _______________________________________________ > Msys2-users mailing list > Msy...@li... > https://lists.sourceforge.net/lists/listinfo/msys2-users > |
From: Jon b. <jon...@gm...> - 2014-05-16 19:54:06
|
Hello everybody, is it possible to get from this libs static versions? openjpeg fontconfig gnutls I can compile them self static, but they are also in the mingw-packages, so maybe it not so complicate to build them for both ways. I never have done a pkg-packages, but when you need help for this libs I can try to do it. Best Regards! Jonathan |
From: Alexey P. <ale...@gm...> - 2014-05-16 03:41:13
|
16 мая 2014 г., в 6:46, Jon <jon...@gm...> написал(а): > I'd like to build a 32-bit static lib for msys2 rather than the msys-2.0.dll from source at > > git://git.code.sf.net/p/msys2/code > > for use with my msys2 install on Win8.1 64-bit. The static lib must be usable from the msys2 `mingw-w64-i686-gcc 4.9.0-4` package. You need to understand that mingw-w64-i686-gcc and msys2-gcc is different compilers. Msys2-gcc is modified Cygwin GCC. Building with msys2-gcc you always get dependency from msys-2.0.dll. At this time there are no static msys-2.0 library only shared. The mingw-w64-i686-gcc is true native windows mingw-w64 toolchain. > > My next step is to build patch.exe from the msys2 source and static link it to msys2 and libgcc so there are no runtime dependencies on `msys-2.0.dll` (115 symbols imported by patch.exe) or `msys-gcc_s-1.dll` (4 symbols imported by patch.exe). I'm hoping the build results in a patch.exe with runtime deps of only kernel32.dll and potentially msvcrt.dll. > I think you need to port patch for mingw-w64. > Is this possible with the current code in the msys2 repo? If yes, what is the best way to get started? > Update packages to latest: pacman -Syu First you may need additional packages to be able build programs with autoconf/automake. I recommend to you install most used develop apps by: pacman -S base-devel You can run MSYS2 with mingw32_shell.bat and install mingw-w64 toolchain: pacman -S mingw-w64-i686-toolchain Then you be able use mingw-w64 compiler to try build any software that you want) Don’t use /usr or / as prefix for mingw programs because this is location only for msys2-packages. By default I use /mingw32 or /mingw64 install prefixes for 32 and 64 bit mingw-packages. > I'd like to be able to build the static libs on my Win8.1 box under msys2, but I'm perfectly fine if I need to cross-build from either Arch or Ubuntu Server. I only have 64-bit installs of those distros. > > You can go to build from msys2) Regards, Alexey. > ------------------------------------------------------------------------------ > "Accelerate Dev Cycles with Automated Cross-Browser Testing - For FREE > Instantly run your Selenium tests across 300+ browser/OS combos. > Get unparalleled scalability from the best Selenium testing platform available > Simple to use. Nothing to install. Get started now for free." > http://p.sf.net/sfu/SauceLabs_______________________________________________ > Msys2-users mailing list > Msy...@li... > https://lists.sourceforge.net/lists/listinfo/msys2-users |
From: Jon <jon...@gm...> - 2014-05-16 02:46:49
|
I'd like to build a 32-bit static lib for msys2 rather than the msys-2.0.dll from source at git://git.code.sf.net/p/msys2/code for use with my msys2 install on Win8.1 64-bit. The static lib must be usable from the msys2 `mingw-w64-i686-gcc 4.9.0-4` package. My next step is to build patch.exe from the msys2 source and static link it to msys2 and libgcc so there are no runtime dependencies on `msys-2.0.dll` (115 symbols imported by patch.exe) or `msys-gcc_s-1.dll` (4 symbols imported by patch.exe). I'm hoping the build results in a patch.exe with runtime deps of only kernel32.dll and potentially msvcrt.dll. Is this possible with the current code in the msys2 repo? If yes, what is the best way to get started? I'd like to be able to build the static libs on my Win8.1 box under msys2, but I'm perfectly fine if I need to cross-build from either Arch or Ubuntu Server. I only have 64-bit installs of those distros. |
From: Alexey P. <ale...@gm...> - 2014-05-15 02:36:37
|
15 мая 2014 г., в 6:34, Jon bae <jon...@gm...> написал(а): > Hello all > > I know windows xp is to old... But I have one how use my build script > under Windows XP, so I try msys2 here in a Virtual Box and when I try to > use cmake it makes nothing. For example: cmake --version show nothing, > it comes directly the input again from the shell. > > When I double click the cmake.exe I get an error with something like: > strerror_s not found in mscrt.dll > > Can I fix that with a new runtime update for windows? Or cmake doesn't > work in generally under xp? > Need a workaround for this issue. > Best Regards > > Jonathan > > > ------------------------------------------------------------------------------ > "Accelerate Dev Cycles with Automated Cross-Browser Testing - For FREE > Instantly run your Selenium tests across 300+ browser/OS combos. > Get unparalleled scalability from the best Selenium testing platform available > Simple to use. Nothing to install. Get started now for free." > http://p.sf.net/sfu/SauceLabs > _______________________________________________ > Msys2-users mailing list > Msy...@li... > https://lists.sourceforge.net/lists/listinfo/msys2-users |
From: Jon b. <jon...@gm...> - 2014-05-15 02:34:26
|
Hello all I know windows xp is to old... But I have one how use my build script under Windows XP, so I try msys2 here in a Virtual Box and when I try to use cmake it makes nothing. For example: cmake --version show nothing, it comes directly the input again from the shell. When I double click the cmake.exe I get an error with something like: strerror_s not found in mscrt.dll Can I fix that with a new runtime update for windows? Or cmake doesn't work in generally under xp? Best Regards Jonathan |
From: Alexey P. <ale...@gm...> - 2014-05-15 02:28:00
|
15 мая 2014 г., в 3:23, Jon bae <jon...@gm...> написал(а): > Hello everybody, > I only want to make a report that gcc 4.9.0 not work with all source > codes correctly. For example when you compile ffmpeg it have a bad flac > decoding. You can test it with the ffmpeg version from msys2 with: > ffmpeg -i input.flac output.wav > > I think it is already on the bug tracker from gcc and ffmpeg. Sad that > is not so easy to select a older mingw/gcc version under msys2, latest > after a pacman update the version goes back to 4.9. But let see how long > it takes for a fix in gcc. > gcc-4.9.0-4 have fix for flac issue. Will rebuild ffmpeg today. But yes new GCC still has other issues . Regards, Alexey. > Best Regards > > Jonathan > > > > ------------------------------------------------------------------------------ > "Accelerate Dev Cycles with Automated Cross-Browser Testing - For FREE > Instantly run your Selenium tests across 300+ browser/OS combos. > Get unparalleled scalability from the best Selenium testing platform available > Simple to use. Nothing to install. Get started now for free." > http://p.sf.net/sfu/SauceLabs > _______________________________________________ > Msys2-users mailing list > Msy...@li... > https://lists.sourceforge.net/lists/listinfo/msys2-users |
From: Jon b. <jon...@gm...> - 2014-05-14 23:23:49
|
Hello everybody, I only want to make a report that gcc 4.9.0 not work with all source codes correctly. For example when you compile ffmpeg it have a bad flac decoding. You can test it with the ffmpeg version from msys2 with: ffmpeg -i input.flac output.wav I think it is already on the bug tracker from gcc and ffmpeg. Sad that is not so easy to select a older mingw/gcc version under msys2, latest after a pacman update the version goes back to 4.9. But let see how long it takes for a fix in gcc. Best Regards Jonathan |
From: Alexey P. <ale...@gm...> - 2014-05-14 16:00:29
|
14 мая 2014 г., в 19:59, Jan Niklas Hasse <jh...@gm...> написал(а): > 2014-05-14 17:54 GMT+02:00 Alexey Pavlov <ale...@gm...>: >> scons that you install via pacman is working with msys-python and need bash for it. >> You can try to build your own scons with mingw-python > > I think you didn't understand me correctly. I'm running scons from bash. > > I've created an issue on Github with steps to reproduce the problem: > https://github.com/Alexpux/MSYS2-packages/issues/9 Ok. I see. Will discuss on github then. |
From: Jan N. H. <jh...@gm...> - 2014-05-14 15:59:33
|
2014-05-14 17:54 GMT+02:00 Alexey Pavlov <ale...@gm...>: > scons that you install via pacman is working with msys-python and need bash for it. > You can try to build your own scons with mingw-python I think you didn't understand me correctly. I'm running scons from bash. I've created an issue on Github with steps to reproduce the problem: https://github.com/Alexpux/MSYS2-packages/issues/9 |
From: Alexey P. <ale...@gm...> - 2014-05-14 15:54:48
|
14 мая 2014 г., в 18:57, Jan Niklas Hasse <jh...@gm...> написал(а): > 2014-05-14 15:34 GMT+02:00 Alexey Pavlov <ale...@gm...>: >> What problem then? > > I don't want to run g++ from bash. I want to use scons. And scons > doesn't seem to find g++ provided by mingw-w64-*-gcc, only the one > provided by gcc (but I don't want to use that one, because it doesn't > work with some other packages and is out of date). > scons that you install via pacman is working with msys-python and need bash for it. You can try to build your own scons with mingw-python Regrads, Alexey. > ------------------------------------------------------------------------------ > "Accelerate Dev Cycles with Automated Cross-Browser Testing - For FREE > Instantly run your Selenium tests across 300+ browser/OS combos. > Get unparalleled scalability from the best Selenium testing platform available > Simple to use. Nothing to install. Get started now for free." > http://p.sf.net/sfu/SauceLabs > _______________________________________________ > Msys2-users mailing list > Msy...@li... > https://lists.sourceforge.net/lists/listinfo/msys2-users |
From: Jan N. H. <jh...@gm...> - 2014-05-14 14:58:02
|
2014-05-14 15:34 GMT+02:00 Alexey Pavlov <ale...@gm...>: > What problem then? I don't want to run g++ from bash. I want to use scons. And scons doesn't seem to find g++ provided by mingw-w64-*-gcc, only the one provided by gcc (but I don't want to use that one, because it doesn't work with some other packages and is out of date). |
From: Alexey P. <ale...@gm...> - 2014-05-14 13:36:05
|
14 мая 2014 г., в 12:54, Jan Niklas Hasse <jh...@gm...> написал(а): > Am 14.05.2014 04:23 schrieb "Alexey Pavlov" <ale...@gm...>: > > > > > > 14 мая 2014 г., в 3:54, Jan Niklas Hasse <jh...@gm...> написал(а): > > > > > Hi! > > > > > > I'm new to MSYS2 and trying to setup my dev environment with it. I've > > > installed scons and mingw-w64-x86_64-gcc with pacman. Although the g++ > > > command works fine, scons can't seem to find it: > > > > > > sh: o: command not found > > > > > > If I install the gcc package scons works, but I want to be able to use > > > the other mingw-w64 packages like boost, etc. > > > Is there anyway to fix this? How are others using scons and mingw-w64? > > > > > to use mingw-w64-x86_64-gcc you need run MSYS2 with mingw64_shell.bat or modify PATH variable > > export PATH=/mingw64/bin:$PATH > > I did run mingw64_shell.bat and g++ is in the path: Running it in bash works fine. > What problem then? |
From: Jan N. H. <jh...@gm...> - 2014-05-14 08:54:17
|
Am 14.05.2014 04:23 schrieb "Alexey Pavlov" <ale...@gm...>: > > > 14 мая 2014 г., в 3:54, Jan Niklas Hasse <jh...@gm...> написал(а): > > > Hi! > > > > I'm new to MSYS2 and trying to setup my dev environment with it. I've > > installed scons and mingw-w64-x86_64-gcc with pacman. Although the g++ > > command works fine, scons can't seem to find it: > > > > sh: o: command not found > > > > If I install the gcc package scons works, but I want to be able to use > > the other mingw-w64 packages like boost, etc. > > Is there anyway to fix this? How are others using scons and mingw-w64? > > > to use mingw-w64-x86_64-gcc you need run MSYS2 with mingw64_shell.bat or modify PATH variable > export PATH=/mingw64/bin:$PATH I did run mingw64_shell.bat and g++ is in the path: Running it in bash works fine. |
From: Alexey P. <ale...@gm...> - 2014-05-14 02:23:07
|
14 мая 2014 г., в 3:54, Jan Niklas Hasse <jh...@gm...> написал(а): > Hi! > > I'm new to MSYS2 and trying to setup my dev environment with it. I've > installed scons and mingw-w64-x86_64-gcc with pacman. Although the g++ > command works fine, scons can't seem to find it: > > sh: o: command not found > > If I install the gcc package scons works, but I want to be able to use > the other mingw-w64 packages like boost, etc. > Is there anyway to fix this? How are others using scons and mingw-w64? > to use mingw-w64-x86_64-gcc you need run MSYS2 with mingw64_shell.bat or modify PATH variable export PATH=/mingw64/bin:$PATH Regards, Alexey. > ------------------------------------------------------------------------------ > "Accelerate Dev Cycles with Automated Cross-Browser Testing - For FREE > Instantly run your Selenium tests across 300+ browser/OS combos. > Get unparalleled scalability from the best Selenium testing platform available > Simple to use. Nothing to install. Get started now for free." > http://p.sf.net/sfu/SauceLabs > _______________________________________________ > Msys2-users mailing list > Msy...@li... > https://lists.sourceforge.net/lists/listinfo/msys2-users |
From: Jan N. H. <jh...@gm...> - 2014-05-13 23:55:11
|
Hi! I'm new to MSYS2 and trying to setup my dev environment with it. I've installed scons and mingw-w64-x86_64-gcc with pacman. Although the g++ command works fine, scons can't seem to find it: sh: o: command not found If I install the gcc package scons works, but I want to be able to use the other mingw-w64 packages like boost, etc. Is there anyway to fix this? How are others using scons and mingw-w64? |
From: Jon b. <jon...@gm...> - 2014-05-07 15:26:18
|
Hello everybody, I the past I unpack the TortoiseHg msi pack in a specified folder, put this in my profile and after that I was able to clone x265 from https://bitbucket.org/multicoreware/x265/wiki/Home and compile it with cmake. Now I try this with the msys2 internal mercurial, but this doesn't work. Normal cmake gets from the hg clone the x265 version number. But mercurial don't build this number, so cmake can not configure right and stop working. Has the msys2 mercurial hg any limitations, or is this a configure problem? I find out that TortoiseHg clone the repo with windows line ending, but mercurial does it with linux line endings, can this be a reason? Best Regards! Jonathan |
From: Alexey P. <al...@gm...> - 2014-05-07 12:04:29
|
2014-05-07 16:03 GMT+04:00 Jon bae <jon...@gm...>: > Thanks Alexey, > it looks like that it works now! But I get this Error now: > undefined reference to `kvz_cpu_cpuid' > Is that a thing from msys2 or from the code? > This is kvazaar issue not MSYS2. > Regards! > Jonathan > > > > 2014-05-07 13:34 GMT+02:00 Alexpux <al...@gm...>: > >> >> 07 мая 2014 г., в 15:13, Alexpux <al...@gm...> написал(а): >> >> >> 07 мая 2014 г., в 14:39, Jon bae <jon...@gm...> написал(а): >> >> You mean the SConstruct? >> https://github.com/ultravideo/kvazaar/blob/master/SConstruct >> >> In only call scons x86 in the folder and get the errors from before. >> >> I found error. Try update packages to get fixed scons. >> >> Regards, >> Alexey. >> >> >> 2014-05-07 12:33 GMT+02:00 Alexpux <al...@gm...>: >>> >>> >>> 07 мая 2014 г., в 14:29, Jon bae <jon...@gm...> написал(а): >>> >>> Hello Alexey, >>> I was trying to compile Kvazaar: >>> https://github.com/ultravideo/kvazaar/releases >>> >>> Under msys1 I was able to compile it normal. But under msys2 it looks >>> like that some things a bit different. Before for example I don't need the >>> --build= and --host= configure parameter, but now I need it. Also mecurial >>> works a bit different. When I use the windows program I get the version >>> number from x265 and cmake is able to compile it, when I try to use the >>> buildin msys2 hgcommand for cloning I don't get any version info and cmake >>> brings errors. But this is a different topic. >>> >>> Show me your build script for it. >>> >>> Best Regards >>> >>> Jonathan >>> >>> >>> >>> 2014-05-07 11:18 GMT+02:00 Alexpux <al...@gm...>: >>>> >>>> >>>> 06 мая 2014 г., в 23:05, Jon bae <jon...@gm...> написал(а): >>>> >>>> > When I try to compile something with scons I get this message: >>>> > scons: Reading SConscript files ... >>>> > EnvironmentError: No module named Actio: >>>> > File "/build32/kvazaar-master/SConstruct", line 19: >>>> > """) >>>> > File "/usr/lib/python2.7/site-packages/SCons/Script/SConscript.py", >>>> > line 607: >>>> > env = self.factory() >>>> > File "/usr/lib/python2.7/site-packages/SCons/Script/SConscript.py", >>>> > line 587: >>>> > default_env = SCons.Defaults.DefaultEnvironment() >>>> > File "/usr/lib/python2.7/site-packages/SCons/Defaults.py", line 88: >>>> > _default_env = SCons.Environment.Environment(*args, **kw) >>>> > File "/usr/lib/python2.7/site-packages/SCons/Environment.py", line >>>> > 1003: >>>> > apply_tools(self, tools, toolpath) >>>> > File "/usr/lib/python2.7/site-packages/SCons/Environment.py", line >>>> > 107: >>>> > env.Tool(tool) >>>> > File "/usr/lib/python2.7/site-packages/SCons/Environment.py", line >>>> > 1787: >>>> > tool(self) >>>> > File "/usr/lib/python2.7/site-packages/SCons/Tool/__init__.py", line >>>> > 183: >>>> > self.generate(env, *args, **kw) >>>> > File "/usr/lib/python2.7/site-packages/SCons/Tool/default.py", line >>>> > 40: >>>> > for t in SCons.Tool.tool_list(env['PLATFORM'], env): >>>> > File "/usr/lib/python2.7/site-packages/SCons/Tool/__init__.py", line >>>> > 801: >>>> > linker = FindTool(linkers, env) or linkers[0] >>>> > File "/usr/lib/python2.7/site-packages/SCons/Tool/__init__.py", line >>>> > 682: >>>> > t = Tool(tool) >>>> > File "/usr/lib/python2.7/site-packages/SCons/Tool/__init__.py", line >>>> > 97: >>>> > module = self._tool_module() >>>> > File "/usr/lib/python2.7/site-packages/SCons/Tool/__init__.py", line >>>> > 148: >>>> > raise SCons.Errors.EnvironmentError(e) >>>> > >>>> > >>>> What program do you try to build? >>>> > >>>> > Am 06.05.2014 20:32, schrieb Alexey Pavlov: >>>> >> 06 мая 2014 г., в 22:30, Jon bae <jon...@gm...> написал(а): >>>> >> >>>> >>> Hello everybody, >>>> >>> is there a special trick to get scons to work? I was thinking I can >>>> >>> use >>>> >>> the msys2 python2 and scons. Is that not right? >>>> >>> >>>> >>> My profile looks like this: >>>> >>> >>>> >>> PYTHONHOME=/usr >>>> >>> PYTHONPATH=/usr/lib/python2.7 >>>> >>> SCONS_LIB_DIR=/usr/lib/python2.7/site-packages >>>> >>> >>>> >>> >>>> >>> PATH=".:/global32/bin:/local32/bin:/mingw32/bin:${MSYS2_PATH}:/opt/bin:/opt/TortoiseHg:${PYTHONHOME}" >>>> >>> export PATH PYTHONPATH >>>> >>> >>>> >> What problems with using SCONS? MSYS2 has its own scons package. >>>> >> See: >>>> >> >>>> >> https://github.com/Alexpux/MINGW-packages/blob/master/mingw-w64-mesa/PKGBUILD#L37 >>>> >> >>>> >> Regards, >>>> >> Alexey. >>>> >> >>>> >>> Best Regards! >>>> >>> >>>> >>> Jonathan >>>> >>> >>>> >>> >>>> >>> >>>> >>> >>>> >>> ------------------------------------------------------------------------------ >>>> >>> Is your legacy SCM system holding you back? Join Perforce May 7 to >>>> >>> find out: >>>> >>> • 3 signs your SCM is hindering your productivity >>>> >>> • Requirements for releasing software faster >>>> >>> • Expert tips and advice for migrating your SCM now >>>> >>> http://p.sf.net/sfu/perforce >>>> >>> _______________________________________________ >>>> >>> Msys2-users mailing list >>>> >>> Msy...@li... >>>> >>> https://lists.sourceforge.net/lists/listinfo/msys2-users >>>> > >>>> > >>>> > >>>> > ------------------------------------------------------------------------------ >>>> > Is your legacy SCM system holding you back? Join Perforce May 7 to >>>> > find out: >>>> > • 3 signs your SCM is hindering your productivity >>>> > • Requirements for releasing software faster >>>> > • Expert tips and advice for migrating your SCM now >>>> > http://p.sf.net/sfu/perforce >>>> > _______________________________________________ >>>> > Msys2-users mailing list >>>> > Msy...@li... >>>> > https://lists.sourceforge.net/lists/listinfo/msys2-users >>>> >>> >>> >> >> >> >> >> >> ------------------------------------------------------------------------------ >> Is your legacy SCM system holding you back? Join Perforce May 7 to find >> out: >> • 3 signs your SCM is hindering your productivity >> • Requirements for releasing software faster >> • Expert tips and advice for migrating your SCM now >> http://p.sf.net/sfu/perforce >> _______________________________________________ >> Msys2-users mailing list >> Msy...@li... >> https://lists.sourceforge.net/lists/listinfo/msys2-users >> > |
From: Jon b. <jon...@gm...> - 2014-05-07 12:03:33
|
Thanks Alexey, it looks like that it works now! But I get this Error now: undefined reference to `kvz_cpu_cpuid' Is that a thing from msys2 or from the code? Regards! Jonathan 2014-05-07 13:34 GMT+02:00 Alexpux <al...@gm...>: > > 07 мая 2014 г., в 15:13, Alexpux <al...@gm...> написал(а): > > > 07 мая 2014 г., в 14:39, Jon bae <jon...@gm...> написал(а): > > You mean the SConstruct? > https://github.com/ultravideo/kvazaar/blob/master/SConstruct > > In only call scons x86 in the folder and get the errors from before. > > I found error. Try update packages to get fixed scons. > > Regards, > Alexey. > > > 2014-05-07 12:33 GMT+02:00 Alexpux <al...@gm...>: > >> >> 07 мая 2014 г., в 14:29, Jon bae <jon...@gm...> написал(а): >> >> Hello Alexey, >> I was trying to compile Kvazaar: >> https://github.com/ultravideo/kvazaar/releases >> >> Under msys1 I was able to compile it normal. But under msys2 it looks >> like that some things a bit different. Before for example I don't need the >> --build= and --host= configure parameter, but now I need it. Also mecurial >> works a bit different. When I use the windows program I get the version >> number from x265 and cmake is able to compile it, when I try to use the >> buildin msys2 hgcommand for cloning I don't get any version info and cmake >> brings errors. But this is a different topic. >> >> Show me your build script for it. >> >> Best Regards >> >> Jonathan >> >> >> >> 2014-05-07 11:18 GMT+02:00 Alexpux <al...@gm...>: >> >>> >>> 06 мая 2014 г., в 23:05, Jon bae <jon...@gm...> написал(а): >>> >>> > When I try to compile something with scons I get this message: >>> > scons: Reading SConscript files ... >>> > EnvironmentError: No module named Actio: >>> > File "/build32/kvazaar-master/SConstruct", line 19: >>> > """) >>> > File "/usr/lib/python2.7/site-packages/SCons/Script/SConscript.py", >>> > line 607: >>> > env = self.factory() >>> > File "/usr/lib/python2.7/site-packages/SCons/Script/SConscript.py", >>> > line 587: >>> > default_env = SCons.Defaults.DefaultEnvironment() >>> > File "/usr/lib/python2.7/site-packages/SCons/Defaults.py", line 88: >>> > _default_env = SCons.Environment.Environment(*args, **kw) >>> > File "/usr/lib/python2.7/site-packages/SCons/Environment.py", line >>> 1003: >>> > apply_tools(self, tools, toolpath) >>> > File "/usr/lib/python2.7/site-packages/SCons/Environment.py", line >>> 107: >>> > env.Tool(tool) >>> > File "/usr/lib/python2.7/site-packages/SCons/Environment.py", line >>> 1787: >>> > tool(self) >>> > File "/usr/lib/python2.7/site-packages/SCons/Tool/__init__.py", line >>> 183: >>> > self.generate(env, *args, **kw) >>> > File "/usr/lib/python2.7/site-packages/SCons/Tool/default.py", line >>> 40: >>> > for t in SCons.Tool.tool_list(env['PLATFORM'], env): >>> > File "/usr/lib/python2.7/site-packages/SCons/Tool/__init__.py", line >>> 801: >>> > linker = FindTool(linkers, env) or linkers[0] >>> > File "/usr/lib/python2.7/site-packages/SCons/Tool/__init__.py", line >>> 682: >>> > t = Tool(tool) >>> > File "/usr/lib/python2.7/site-packages/SCons/Tool/__init__.py", line >>> 97: >>> > module = self._tool_module() >>> > File "/usr/lib/python2.7/site-packages/SCons/Tool/__init__.py", line >>> 148: >>> > raise SCons.Errors.EnvironmentError(e) >>> > >>> > >>> What program do you try to build? >>> > >>> > Am 06.05.2014 20:32, schrieb Alexey Pavlov: >>> >> 06 мая 2014 г., в 22:30, Jon bae <jon...@gm...> написал(а): >>> >> >>> >>> Hello everybody, >>> >>> is there a special trick to get scons to work? I was thinking I can >>> use >>> >>> the msys2 python2 and scons. Is that not right? >>> >>> >>> >>> My profile looks like this: >>> >>> >>> >>> PYTHONHOME=/usr >>> >>> PYTHONPATH=/usr/lib/python2.7 >>> >>> SCONS_LIB_DIR=/usr/lib/python2.7/site-packages >>> >>> >>> >>> >>> PATH=".:/global32/bin:/local32/bin:/mingw32/bin:${MSYS2_PATH}:/opt/bin:/opt/TortoiseHg:${PYTHONHOME}" >>> >>> export PATH PYTHONPATH >>> >>> >>> >> What problems with using SCONS? MSYS2 has its own scons package. >>> >> See: >>> >> >>> https://github.com/Alexpux/MINGW-packages/blob/master/mingw-w64-mesa/PKGBUILD#L37 >>> >> >>> >> Regards, >>> >> Alexey. >>> >> >>> >>> Best Regards! >>> >>> >>> >>> Jonathan >>> >>> >>> >>> >>> >>> >>> >>> >>> ------------------------------------------------------------------------------ >>> >>> Is your legacy SCM system holding you back? Join Perforce May 7 to >>> find out: >>> >>> • 3 signs your SCM is hindering your productivity >>> >>> • Requirements for releasing software faster >>> >>> • Expert tips and advice for migrating your SCM now >>> >>> http://p.sf.net/sfu/perforce >>> >>> _______________________________________________ >>> >>> Msys2-users mailing list >>> >>> Msy...@li... >>> >>> https://lists.sourceforge.net/lists/listinfo/msys2-users >>> > >>> > >>> > >>> ------------------------------------------------------------------------------ >>> > Is your legacy SCM system holding you back? Join Perforce May 7 to >>> find out: >>> > • 3 signs your SCM is hindering your productivity >>> > • Requirements for releasing software faster >>> > • Expert tips and advice for migrating your SCM now >>> > http://p.sf.net/sfu/perforce >>> > _______________________________________________ >>> > Msys2-users mailing list >>> > Msy...@li... >>> > https://lists.sourceforge.net/lists/listinfo/msys2-users >>> >>> >> >> > > > > > ------------------------------------------------------------------------------ > Is your legacy SCM system holding you back? Join Perforce May 7 to find > out: > • 3 signs your SCM is hindering your productivity > • Requirements for releasing software faster > • Expert tips and advice for migrating your SCM now > http://p.sf.net/sfu/perforce > _______________________________________________ > Msys2-users mailing list > Msy...@li... > https://lists.sourceforge.net/lists/listinfo/msys2-users > > |
From: Alexpux <al...@gm...> - 2014-05-07 11:35:08
|
07 мая 2014 г., в 15:13, Alexpux <al...@gm...> написал(а): > > 07 мая 2014 г., в 14:39, Jon bae <jon...@gm...> написал(а): > >> You mean the SConstruct? >> https://github.com/ultravideo/kvazaar/blob/master/SConstruct >> >> In only call scons x86 in the folder and get the errors from before. >> > I found error. Try update packages to get fixed scons. > > Regards, > Alexey. > >> >> 2014-05-07 12:33 GMT+02:00 Alexpux <al...@gm...>: >> >> 07 мая 2014 г., в 14:29, Jon bae <jon...@gm...> написал(а): >> >>> Hello Alexey, >>> I was trying to compile Kvazaar: >>> https://github.com/ultravideo/kvazaar/releases >>> >>> Under msys1 I was able to compile it normal. But under msys2 it looks like that some things a bit different. Before for example I don't need the --build= and --host= configure parameter, but now I need it. Also mecurial works a bit different. When I use the windows program I get the version number from x265 and cmake is able to compile it, when I try to use the buildin msys2 hgcommand for cloning I don't get any version info and cmake brings errors. But this is a different topic. >>> >> Show me your build script for it. >> >>> Best Regards >>> >>> Jonathan >>> >>> >>> >>> 2014-05-07 11:18 GMT+02:00 Alexpux <al...@gm...>: >>> >>> 06 мая 2014 г., в 23:05, Jon bae <jon...@gm...> написал(а): >>> >>> > When I try to compile something with scons I get this message: >>> > scons: Reading SConscript files ... >>> > EnvironmentError: No module named Actio: >>> > File "/build32/kvazaar-master/SConstruct", line 19: >>> > """) >>> > File "/usr/lib/python2.7/site-packages/SCons/Script/SConscript.py", >>> > line 607: >>> > env = self.factory() >>> > File "/usr/lib/python2.7/site-packages/SCons/Script/SConscript.py", >>> > line 587: >>> > default_env = SCons.Defaults.DefaultEnvironment() >>> > File "/usr/lib/python2.7/site-packages/SCons/Defaults.py", line 88: >>> > _default_env = SCons.Environment.Environment(*args, **kw) >>> > File "/usr/lib/python2.7/site-packages/SCons/Environment.py", line 1003: >>> > apply_tools(self, tools, toolpath) >>> > File "/usr/lib/python2.7/site-packages/SCons/Environment.py", line 107: >>> > env.Tool(tool) >>> > File "/usr/lib/python2.7/site-packages/SCons/Environment.py", line 1787: >>> > tool(self) >>> > File "/usr/lib/python2.7/site-packages/SCons/Tool/__init__.py", line 183: >>> > self.generate(env, *args, **kw) >>> > File "/usr/lib/python2.7/site-packages/SCons/Tool/default.py", line 40: >>> > for t in SCons.Tool.tool_list(env['PLATFORM'], env): >>> > File "/usr/lib/python2.7/site-packages/SCons/Tool/__init__.py", line 801: >>> > linker = FindTool(linkers, env) or linkers[0] >>> > File "/usr/lib/python2.7/site-packages/SCons/Tool/__init__.py", line 682: >>> > t = Tool(tool) >>> > File "/usr/lib/python2.7/site-packages/SCons/Tool/__init__.py", line 97: >>> > module = self._tool_module() >>> > File "/usr/lib/python2.7/site-packages/SCons/Tool/__init__.py", line 148: >>> > raise SCons.Errors.EnvironmentError(e) >>> > >>> > >>> What program do you try to build? >>> > >>> > Am 06.05.2014 20:32, schrieb Alexey Pavlov: >>> >> 06 мая 2014 г., в 22:30, Jon bae <jon...@gm...> написал(а): >>> >> >>> >>> Hello everybody, >>> >>> is there a special trick to get scons to work? I was thinking I can use >>> >>> the msys2 python2 and scons. Is that not right? >>> >>> >>> >>> My profile looks like this: >>> >>> >>> >>> PYTHONHOME=/usr >>> >>> PYTHONPATH=/usr/lib/python2.7 >>> >>> SCONS_LIB_DIR=/usr/lib/python2.7/site-packages >>> >>> >>> >>> PATH=".:/global32/bin:/local32/bin:/mingw32/bin:${MSYS2_PATH}:/opt/bin:/opt/TortoiseHg:${PYTHONHOME}" >>> >>> export PATH PYTHONPATH >>> >>> >>> >> What problems with using SCONS? MSYS2 has its own scons package. >>> >> See: >>> >> https://github.com/Alexpux/MINGW-packages/blob/master/mingw-w64-mesa/PKGBUILD#L37 >>> >> >>> >> Regards, >>> >> Alexey. >>> >> >>> >>> Best Regards! >>> >>> >>> >>> Jonathan >>> >>> >>> >>> >>> >>> >>> >>> ------------------------------------------------------------------------------ >>> >>> Is your legacy SCM system holding you back? Join Perforce May 7 to find out: >>> >>> • 3 signs your SCM is hindering your productivity >>> >>> • Requirements for releasing software faster >>> >>> • Expert tips and advice for migrating your SCM now >>> >>> http://p.sf.net/sfu/perforce >>> >>> _______________________________________________ >>> >>> Msys2-users mailing list >>> >>> Msy...@li... >>> >>> https://lists.sourceforge.net/lists/listinfo/msys2-users >>> > >>> > >>> > ------------------------------------------------------------------------------ >>> > Is your legacy SCM system holding you back? Join Perforce May 7 to find out: >>> > • 3 signs your SCM is hindering your productivity >>> > • Requirements for releasing software faster >>> > • Expert tips and advice for migrating your SCM now >>> > http://p.sf.net/sfu/perforce >>> > _______________________________________________ >>> > Msys2-users mailing list >>> > Msy...@li... >>> > https://lists.sourceforge.net/lists/listinfo/msys2-users >>> >>> >> >> > |
From: Ray D. <min...@gm...> - 2014-05-07 11:34:02
|
PATH=".:/global32/bin:/local32/bin:/mingw32/bin:${MSYS2_PATH}:/opt/bin:/opt/TortoiseHg:${PYTHONHOME}" ^ You may be asking for trouble with that path, unless global32/bin and local32/bin only contain MSYS2-built packages. On Wed, May 7, 2014 at 10:18 AM, Alexpux <al...@gm...> wrote: > > 06 мая 2014 г., в 23:05, Jon bae <jon...@gm...> написал(а): > >> When I try to compile something with scons I get this message: >> scons: Reading SConscript files ... >> EnvironmentError: No module named Actio: >> File "/build32/kvazaar-master/SConstruct", line 19: >> """) >> File "/usr/lib/python2.7/site-packages/SCons/Script/SConscript.py", >> line 607: >> env = self.factory() >> File "/usr/lib/python2.7/site-packages/SCons/Script/SConscript.py", >> line 587: >> default_env = SCons.Defaults.DefaultEnvironment() >> File "/usr/lib/python2.7/site-packages/SCons/Defaults.py", line 88: >> _default_env = SCons.Environment.Environment(*args, **kw) >> File "/usr/lib/python2.7/site-packages/SCons/Environment.py", line 1003: >> apply_tools(self, tools, toolpath) >> File "/usr/lib/python2.7/site-packages/SCons/Environment.py", line 107: >> env.Tool(tool) >> File "/usr/lib/python2.7/site-packages/SCons/Environment.py", line 1787: >> tool(self) >> File "/usr/lib/python2.7/site-packages/SCons/Tool/__init__.py", line 183: >> self.generate(env, *args, **kw) >> File "/usr/lib/python2.7/site-packages/SCons/Tool/default.py", line 40: >> for t in SCons.Tool.tool_list(env['PLATFORM'], env): >> File "/usr/lib/python2.7/site-packages/SCons/Tool/__init__.py", line 801: >> linker = FindTool(linkers, env) or linkers[0] >> File "/usr/lib/python2.7/site-packages/SCons/Tool/__init__.py", line 682: >> t = Tool(tool) >> File "/usr/lib/python2.7/site-packages/SCons/Tool/__init__.py", line 97: >> module = self._tool_module() >> File "/usr/lib/python2.7/site-packages/SCons/Tool/__init__.py", line 148: >> raise SCons.Errors.EnvironmentError(e) >> >> > What program do you try to build? >> >> Am 06.05.2014 20:32, schrieb Alexey Pavlov: >>> 06 мая 2014 г., в 22:30, Jon bae <jon...@gm...> написал(а): >>> >>>> Hello everybody, >>>> is there a special trick to get scons to work? I was thinking I can use >>>> the msys2 python2 and scons. Is that not right? >>>> >>>> My profile looks like this: >>>> >>>> PYTHONHOME=/usr >>>> PYTHONPATH=/usr/lib/python2.7 >>>> SCONS_LIB_DIR=/usr/lib/python2.7/site-packages >>>> >>>> PATH=".:/global32/bin:/local32/bin:/mingw32/bin:${MSYS2_PATH}:/opt/bin:/opt/TortoiseHg:${PYTHONHOME}" >>>> export PATH PYTHONPATH >>>> >>> What problems with using SCONS? MSYS2 has its own scons package. >>> See: >>> https://github.com/Alexpux/MINGW-packages/blob/master/mingw-w64-mesa/PKGBUILD#L37 >>> >>> Regards, >>> Alexey. >>> >>>> Best Regards! >>>> >>>> Jonathan >>>> >>>> >>>> >>>> ------------------------------------------------------------------------------ >>>> Is your legacy SCM system holding you back? Join Perforce May 7 to find out: >>>> • 3 signs your SCM is hindering your productivity >>>> • Requirements for releasing software faster >>>> • Expert tips and advice for migrating your SCM now >>>> http://p.sf.net/sfu/perforce >>>> _______________________________________________ >>>> Msys2-users mailing list >>>> Msy...@li... >>>> https://lists.sourceforge.net/lists/listinfo/msys2-users >> >> >> ------------------------------------------------------------------------------ >> Is your legacy SCM system holding you back? Join Perforce May 7 to find out: >> • 3 signs your SCM is hindering your productivity >> • Requirements for releasing software faster >> • Expert tips and advice for migrating your SCM now >> http://p.sf.net/sfu/perforce >> _______________________________________________ >> Msys2-users mailing list >> Msy...@li... >> https://lists.sourceforge.net/lists/listinfo/msys2-users > > > ------------------------------------------------------------------------------ > Is your legacy SCM system holding you back? Join Perforce May 7 to find out: > • 3 signs your SCM is hindering your productivity > • Requirements for releasing software faster > • Expert tips and advice for migrating your SCM now > http://p.sf.net/sfu/perforce > _______________________________________________ > Msys2-users mailing list > Msy...@li... > https://lists.sourceforge.net/lists/listinfo/msys2-users |
From: Alexpux <al...@gm...> - 2014-05-07 10:33:24
|
07 мая 2014 г., в 14:29, Jon bae <jon...@gm...> написал(а): > Hello Alexey, > I was trying to compile Kvazaar: > https://github.com/ultravideo/kvazaar/releases > > Under msys1 I was able to compile it normal. But under msys2 it looks like that some things a bit different. Before for example I don't need the --build= and --host= configure parameter, but now I need it. Also mecurial works a bit different. When I use the windows program I get the version number from x265 and cmake is able to compile it, when I try to use the buildin msys2 hgcommand for cloning I don't get any version info and cmake brings errors. But this is a different topic. > Show me your build script for it. > Best Regards > > Jonathan > > > > 2014-05-07 11:18 GMT+02:00 Alexpux <al...@gm...>: > > 06 мая 2014 г., в 23:05, Jon bae <jon...@gm...> написал(а): > > > When I try to compile something with scons I get this message: > > scons: Reading SConscript files ... > > EnvironmentError: No module named Actio: > > File "/build32/kvazaar-master/SConstruct", line 19: > > """) > > File "/usr/lib/python2.7/site-packages/SCons/Script/SConscript.py", > > line 607: > > env = self.factory() > > File "/usr/lib/python2.7/site-packages/SCons/Script/SConscript.py", > > line 587: > > default_env = SCons.Defaults.DefaultEnvironment() > > File "/usr/lib/python2.7/site-packages/SCons/Defaults.py", line 88: > > _default_env = SCons.Environment.Environment(*args, **kw) > > File "/usr/lib/python2.7/site-packages/SCons/Environment.py", line 1003: > > apply_tools(self, tools, toolpath) > > File "/usr/lib/python2.7/site-packages/SCons/Environment.py", line 107: > > env.Tool(tool) > > File "/usr/lib/python2.7/site-packages/SCons/Environment.py", line 1787: > > tool(self) > > File "/usr/lib/python2.7/site-packages/SCons/Tool/__init__.py", line 183: > > self.generate(env, *args, **kw) > > File "/usr/lib/python2.7/site-packages/SCons/Tool/default.py", line 40: > > for t in SCons.Tool.tool_list(env['PLATFORM'], env): > > File "/usr/lib/python2.7/site-packages/SCons/Tool/__init__.py", line 801: > > linker = FindTool(linkers, env) or linkers[0] > > File "/usr/lib/python2.7/site-packages/SCons/Tool/__init__.py", line 682: > > t = Tool(tool) > > File "/usr/lib/python2.7/site-packages/SCons/Tool/__init__.py", line 97: > > module = self._tool_module() > > File "/usr/lib/python2.7/site-packages/SCons/Tool/__init__.py", line 148: > > raise SCons.Errors.EnvironmentError(e) > > > > > What program do you try to build? > > > > Am 06.05.2014 20:32, schrieb Alexey Pavlov: > >> 06 мая 2014 г., в 22:30, Jon bae <jon...@gm...> написал(а): > >> > >>> Hello everybody, > >>> is there a special trick to get scons to work? I was thinking I can use > >>> the msys2 python2 and scons. Is that not right? > >>> > >>> My profile looks like this: > >>> > >>> PYTHONHOME=/usr > >>> PYTHONPATH=/usr/lib/python2.7 > >>> SCONS_LIB_DIR=/usr/lib/python2.7/site-packages > >>> > >>> PATH=".:/global32/bin:/local32/bin:/mingw32/bin:${MSYS2_PATH}:/opt/bin:/opt/TortoiseHg:${PYTHONHOME}" > >>> export PATH PYTHONPATH > >>> > >> What problems with using SCONS? MSYS2 has its own scons package. > >> See: > >> https://github.com/Alexpux/MINGW-packages/blob/master/mingw-w64-mesa/PKGBUILD#L37 > >> > >> Regards, > >> Alexey. > >> > >>> Best Regards! > >>> > >>> Jonathan > >>> > >>> > >>> > >>> ------------------------------------------------------------------------------ > >>> Is your legacy SCM system holding you back? Join Perforce May 7 to find out: > >>> • 3 signs your SCM is hindering your productivity > >>> • Requirements for releasing software faster > >>> • Expert tips and advice for migrating your SCM now > >>> http://p.sf.net/sfu/perforce > >>> _______________________________________________ > >>> Msys2-users mailing list > >>> Msy...@li... > >>> https://lists.sourceforge.net/lists/listinfo/msys2-users > > > > > > ------------------------------------------------------------------------------ > > Is your legacy SCM system holding you back? Join Perforce May 7 to find out: > > • 3 signs your SCM is hindering your productivity > > • Requirements for releasing software faster > > • Expert tips and advice for migrating your SCM now > > http://p.sf.net/sfu/perforce > > _______________________________________________ > > Msys2-users mailing list > > Msy...@li... > > https://lists.sourceforge.net/lists/listinfo/msys2-users > > |
From: Jon b. <jon...@gm...> - 2014-05-07 10:29:58
|
Hello Alexey, I was trying to compile Kvazaar: https://github.com/ultravideo/kvazaar/releases Under msys1 I was able to compile it normal. But under msys2 it looks like that some things a bit different. Before for example I don't need the --build= and --host= configure parameter, but now I need it. Also mecurial works a bit different. When I use the windows program I get the version number from x265 and cmake is able to compile it, when I try to use the buildin msys2 hgcommand for cloning I don't get any version info and cmake brings errors. But this is a different topic. Best Regards Jonathan 2014-05-07 11:18 GMT+02:00 Alexpux <al...@gm...>: > > 06 мая 2014 г., в 23:05, Jon bae <jon...@gm...> написал(а): > > > When I try to compile something with scons I get this message: > > scons: Reading SConscript files ... > > EnvironmentError: No module named Actio: > > File "/build32/kvazaar-master/SConstruct", line 19: > > """) > > File "/usr/lib/python2.7/site-packages/SCons/Script/SConscript.py", > > line 607: > > env = self.factory() > > File "/usr/lib/python2.7/site-packages/SCons/Script/SConscript.py", > > line 587: > > default_env = SCons.Defaults.DefaultEnvironment() > > File "/usr/lib/python2.7/site-packages/SCons/Defaults.py", line 88: > > _default_env = SCons.Environment.Environment(*args, **kw) > > File "/usr/lib/python2.7/site-packages/SCons/Environment.py", line > 1003: > > apply_tools(self, tools, toolpath) > > File "/usr/lib/python2.7/site-packages/SCons/Environment.py", line 107: > > env.Tool(tool) > > File "/usr/lib/python2.7/site-packages/SCons/Environment.py", line > 1787: > > tool(self) > > File "/usr/lib/python2.7/site-packages/SCons/Tool/__init__.py", line > 183: > > self.generate(env, *args, **kw) > > File "/usr/lib/python2.7/site-packages/SCons/Tool/default.py", line 40: > > for t in SCons.Tool.tool_list(env['PLATFORM'], env): > > File "/usr/lib/python2.7/site-packages/SCons/Tool/__init__.py", line > 801: > > linker = FindTool(linkers, env) or linkers[0] > > File "/usr/lib/python2.7/site-packages/SCons/Tool/__init__.py", line > 682: > > t = Tool(tool) > > File "/usr/lib/python2.7/site-packages/SCons/Tool/__init__.py", line > 97: > > module = self._tool_module() > > File "/usr/lib/python2.7/site-packages/SCons/Tool/__init__.py", line > 148: > > raise SCons.Errors.EnvironmentError(e) > > > > > What program do you try to build? > > > > Am 06.05.2014 20:32, schrieb Alexey Pavlov: > >> 06 мая 2014 г., в 22:30, Jon bae <jon...@gm...> написал(а): > >> > >>> Hello everybody, > >>> is there a special trick to get scons to work? I was thinking I can use > >>> the msys2 python2 and scons. Is that not right? > >>> > >>> My profile looks like this: > >>> > >>> PYTHONHOME=/usr > >>> PYTHONPATH=/usr/lib/python2.7 > >>> SCONS_LIB_DIR=/usr/lib/python2.7/site-packages > >>> > >>> > PATH=".:/global32/bin:/local32/bin:/mingw32/bin:${MSYS2_PATH}:/opt/bin:/opt/TortoiseHg:${PYTHONHOME}" > >>> export PATH PYTHONPATH > >>> > >> What problems with using SCONS? MSYS2 has its own scons package. > >> See: > >> > https://github.com/Alexpux/MINGW-packages/blob/master/mingw-w64-mesa/PKGBUILD#L37 > >> > >> Regards, > >> Alexey. > >> > >>> Best Regards! > >>> > >>> Jonathan > >>> > >>> > >>> > >>> > ------------------------------------------------------------------------------ > >>> Is your legacy SCM system holding you back? Join Perforce May 7 to > find out: > >>> • 3 signs your SCM is hindering your productivity > >>> • Requirements for releasing software faster > >>> • Expert tips and advice for migrating your SCM now > >>> http://p.sf.net/sfu/perforce > >>> _______________________________________________ > >>> Msys2-users mailing list > >>> Msy...@li... > >>> https://lists.sourceforge.net/lists/listinfo/msys2-users > > > > > > > ------------------------------------------------------------------------------ > > Is your legacy SCM system holding you back? Join Perforce May 7 to find > out: > > • 3 signs your SCM is hindering your productivity > > • Requirements for releasing software faster > > • Expert tips and advice for migrating your SCM now > > http://p.sf.net/sfu/perforce > > _______________________________________________ > > Msys2-users mailing list > > Msy...@li... > > https://lists.sourceforge.net/lists/listinfo/msys2-users > > |
From: Alexpux <al...@gm...> - 2014-05-07 09:18:45
|
06 мая 2014 г., в 23:05, Jon bae <jon...@gm...> написал(а): > When I try to compile something with scons I get this message: > scons: Reading SConscript files ... > EnvironmentError: No module named Actio: > File "/build32/kvazaar-master/SConstruct", line 19: > """) > File "/usr/lib/python2.7/site-packages/SCons/Script/SConscript.py", > line 607: > env = self.factory() > File "/usr/lib/python2.7/site-packages/SCons/Script/SConscript.py", > line 587: > default_env = SCons.Defaults.DefaultEnvironment() > File "/usr/lib/python2.7/site-packages/SCons/Defaults.py", line 88: > _default_env = SCons.Environment.Environment(*args, **kw) > File "/usr/lib/python2.7/site-packages/SCons/Environment.py", line 1003: > apply_tools(self, tools, toolpath) > File "/usr/lib/python2.7/site-packages/SCons/Environment.py", line 107: > env.Tool(tool) > File "/usr/lib/python2.7/site-packages/SCons/Environment.py", line 1787: > tool(self) > File "/usr/lib/python2.7/site-packages/SCons/Tool/__init__.py", line 183: > self.generate(env, *args, **kw) > File "/usr/lib/python2.7/site-packages/SCons/Tool/default.py", line 40: > for t in SCons.Tool.tool_list(env['PLATFORM'], env): > File "/usr/lib/python2.7/site-packages/SCons/Tool/__init__.py", line 801: > linker = FindTool(linkers, env) or linkers[0] > File "/usr/lib/python2.7/site-packages/SCons/Tool/__init__.py", line 682: > t = Tool(tool) > File "/usr/lib/python2.7/site-packages/SCons/Tool/__init__.py", line 97: > module = self._tool_module() > File "/usr/lib/python2.7/site-packages/SCons/Tool/__init__.py", line 148: > raise SCons.Errors.EnvironmentError(e) > > What program do you try to build? > > Am 06.05.2014 20:32, schrieb Alexey Pavlov: >> 06 мая 2014 г., в 22:30, Jon bae <jon...@gm...> написал(а): >> >>> Hello everybody, >>> is there a special trick to get scons to work? I was thinking I can use >>> the msys2 python2 and scons. Is that not right? >>> >>> My profile looks like this: >>> >>> PYTHONHOME=/usr >>> PYTHONPATH=/usr/lib/python2.7 >>> SCONS_LIB_DIR=/usr/lib/python2.7/site-packages >>> >>> PATH=".:/global32/bin:/local32/bin:/mingw32/bin:${MSYS2_PATH}:/opt/bin:/opt/TortoiseHg:${PYTHONHOME}" >>> export PATH PYTHONPATH >>> >> What problems with using SCONS? MSYS2 has its own scons package. >> See: >> https://github.com/Alexpux/MINGW-packages/blob/master/mingw-w64-mesa/PKGBUILD#L37 >> >> Regards, >> Alexey. >> >>> Best Regards! >>> >>> Jonathan >>> >>> >>> >>> ------------------------------------------------------------------------------ >>> Is your legacy SCM system holding you back? Join Perforce May 7 to find out: >>> • 3 signs your SCM is hindering your productivity >>> • Requirements for releasing software faster >>> • Expert tips and advice for migrating your SCM now >>> http://p.sf.net/sfu/perforce >>> _______________________________________________ >>> Msys2-users mailing list >>> Msy...@li... >>> https://lists.sourceforge.net/lists/listinfo/msys2-users > > > ------------------------------------------------------------------------------ > Is your legacy SCM system holding you back? Join Perforce May 7 to find out: > • 3 signs your SCM is hindering your productivity > • Requirements for releasing software faster > • Expert tips and advice for migrating your SCM now > http://p.sf.net/sfu/perforce > _______________________________________________ > Msys2-users mailing list > Msy...@li... > https://lists.sourceforge.net/lists/listinfo/msys2-users |
From: Ray D. <min...@gm...> - 2014-05-07 06:52:41
|
That's great, Could I trouble you to make the PKGBUILD files for botan and monotone? This makes it really easy for others to build from source? For lots of reference see: https://github.com/Alexpux/MINGW-packages On Wed, May 7, 2014 at 7:39 AM, Stephen Leake <ste...@st...> wrote: > For the record, monotone is now compiling successfully with > msys2/mingw64 and msys2/mingw32. Attached are the install instructions. > > -- > -- Stephe > > See INSTALL for general notes, such as running 'make' and 'make check' > > on Windows (using MinGW64 64 bit via Msys2): > > Here we give sources for the various packages needed. We give > directions to the download, rather than an exact URL, to make it easy > to check for new versions. > > The versions given here may not be exactly the same versions as used to > build the current release of monontone. > > These instructions work on a new computer, with only > 64 bit Windows 7 installed. > > Msys2 provides all of the tools required, and several of the packages. > > Package | Version | location > -------------------------- > msys2 64 bit | | http://sourceforge.net/p/msys2/wiki/MSYS2%20installation/ > | | Downloading | 64-bit | latest version > botan | 1.10.8 | http://botan.randombit.net/download.html > | "Source: >tar/bzip<" under "Current Stable Release" > | _not_ the "windows binary installer" > Depends.exe | | http://www.dependencywalker.com/ ; also comes with Visual Studio > > The tools listed here are sufficient to build the monotone > executable and html and info documentation. However, the > 'distcheck' target also builds the documentation in > postscript format, which requires tools not (yet) available > for MinGW. FIXME: verify > > The commands below assume you download files to ~/Downloads. > > FIXME: replace this file with an msys2 PKGBUILD > > 01. MSYS2 > following instructions at http://sourceforge.net/p/msys2/wiki/MSYS2%20installation/ > > more detailed instruction at http://sourceforge.net/p/msys2/tickets/32/?limit=10&page=1#216b > > for more help, consult the mailing list at https://lists.sourceforge.net/lists/listinfo/msys2-users > > Create directory c:/Msys2 > > using 7-zip or Cygwin tar, unpack msys2-base-x86_64-20140216.tar.xz to c:/Msys2 > > from cmd.exe (_not_ Windows Explorer), run c:\Msys2\msys64\msys2_shell.bat > that starts an msys shell; exit it. > > start cmd.exe again, run c:\Msys2\msys64\msys2_shell.bat again > > in the msys64 shell, run 'pacman -Syu'. that gives errors about rebase. Exit the shell. > > in cmd.exe, run c:\Msys2\msys64\autorebase.bat > > in cmd.exe, run c:\Msys2\msys64\msys2_shell.bat > > in the msys shell: > > $ pacman -S mingw-w64-x86_64-toolchain > # install all (just hit return) > # IMPROVEME; don't need all of that > # but 'pacman -Qo g++' gives 'error: No package owns /usr/mingw64/bin/g++' > > $ pacman -S autoconf automake > $ pacman -S mingw64/mingw-w64-x86_64-sqlite3 mingw64/mingw-w64-x86_64-boost > $ pacman -S mingw64/mingw-w64-x86_64-lua mingw64/mingw-w64-x86_64-libidn > $ pacman -S mingw64/mingw-w64-x86_64-pcre > $ pacman -S msys/tar msys/make > > 02. botan > $ mkdir /usr/src > $ cd /usr/src > $ export PATH=/mingw32/bin:$PATH > $ tar xf ~/Downloads/Botan-1.10.8.tbz > $ cd Botan-1.10.8 > $ ./configure.py --prefix=/mingw64 --cc=gcc --os=mingw --cpu=x86_64 > $ make install > > 03. Depends.exe > If you have Visual Studio installed, you should be able to skip this. > If you don't, then download the appropriate depends*.zip and > unpack it someplace in your %PATH% (for example, C:\MinGW\bin\). > This is only used by the testsuite, in particular the empty_environment test. > If you just want to build monotone for your own use, you can skip this and > just ignore that test failing. > > 04. build monotone > $ export PATH=/mingw32/bin:$PATH > $ cd /c/Projects/monotone > $ autoreconf -i # not needed if you use the distributed tarball > $ export botan_CFLAGS="-I/mingw64/include/botan-1.10" > $ export botan_LIBS="-lbotan-1.10" > $ ./configure > $ make > > See innosetup/README.txt for instructions on building the native Win32 installer. > > (ediff "INSTALL_windows_msys2_32.txt" INSTALL_windows_msys2_64.txt") > > ------------------------------------------------------------------------------ > Is your legacy SCM system holding you back? Join Perforce May 7 to find out: > • 3 signs your SCM is hindering your productivity > • Requirements for releasing software faster > • Expert tips and advice for migrating your SCM now > http://p.sf.net/sfu/perforce > _______________________________________________ > Msys2-users mailing list > Msy...@li... > https://lists.sourceforge.net/lists/listinfo/msys2-users > |