2014-05-07 16:03 GMT+04:00 Jon bae <[email protected]>: > 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 <[email protected]>: > >> >> 07 мая 2014 г., в 15:13, Alexpux <[email protected]> написал(а): >> >> >> 07 мая 2014 г., в 14:39, Jon bae <[email protected]> написал(а): >> >> 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 <[email protected]>: >>> >>> >>> 07 мая 2014 г., в 14:29, Jon bae <[email protected]> написал(а): >>> >>> 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 <[email protected]>: >>>> >>>> >>>> 06 мая 2014 г., в 23:05, Jon bae <[email protected]> написал(а): >>>> >>>> > 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 <[email protected]> написал(а): >>>> >> >>>> >>> 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 >>>> >>> [email protected] >>>> >>> 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 >>>> > [email protected] >>>> > 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 >> [email protected] >> 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 [email protected] https://lists.sourceforge.net/lists/listinfo/msys2-users
