|
From: | Arturo Rinaldi |
Subject: | Re: [Discuss-gnuradio] Status of GNU Radio with OSX 10.9 |
Date: | Tue, 03 Dec 2013 02:33:10 +0100 |
User-agent: | Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:24.0) Gecko/20100101 Thunderbird/24.1.1 |
Il 02/12/13 22:15, Michael Dickens ha
scritto:
ok let's sum up and see if i have understood what is coded in the Portfile. Let's examine it case by case :Hi Arturo - You don't need all 8 diff files. If you read through the Portfile for GNU Radio, you'll find that you need just 5 of those patches to build 3.6.5.1 on 10.9; if you want to build on 10.8, you need just 3. Needed for 10.8 and 10.9 (and, likely, 10.7 or earlier): patch-path-order.diff patch-volk_lib_CMakeLists.txt.legacy.diff patch-volk_gen_archs.xml.legacy.diff Needed just for 10.9/libc++: patch-gnuradio-core_swig_std_std_container.i.diff patch-gnuradio-core_swig_include-std_string.i.diff If you use those patches on your OOT build of GNU Radio, you should be able to build it with minimal defines added to the cmake command line. - MLD On Dec 2, 2013, at 2:23 PM, Arturo Rinaldi <address@hidden> wrote:mmm I see.....ok let's do it this way. Let's say that i untar the 3.6.5.1 tarball and write a script that patches all the needed files before running the usual steps of configuration. If I have understood well what I have to do I need to use all the 8 diff files you uploaded on the macports server, join them and apply the result to the extracted tarball directory. I can try that with patch --dry-run to find if the patching is properly perfromed and the files are not affected by patching. Now i have to figure out which are the right diff files to patch the legacy version and the new version since I'm noticing that the source path structure is different in the new tarball. Do I have to use all of them or not ? Can i write just one single diff file to apply before building from source as usual ? I was thinlking thah once the work is finished i could post it on the mailing list so it'd be available for everyone.....let me know if you like the idea. 10.7 LEGACY (3.6.5.1 and lower) and cat of : patch-path-order.diff patch-volk_lib_CMakeLists.txt.legacy.diff patch-volk_gen_archs.xml.legacy.diff then apply resulting patch, then build as usual PS : I have always built from source any latest tarball of gnuradio legacy successfully, so I don't think I'll ever apply this modifications NEW releases (3.7 and above) nothing to patch or to modify 10.8 LEGACY (3.6.5.1 and lower) and cat of : patch-path-order.diff patch-volk_lib_CMakeLists.txt.legacy.diff patch-volk_gen_archs.xml.legacy.diff then apply resulting patch, then build as usual NEW releases (3.7 and above) nothing to patch or to modify (at least applying the swig/std "trick" but it seems working without it as well) 10.9 first of all I have to perform the copy of the directory std of SWIG in my source directory according to : LEGACY (3.6.5.1 and lower) cp -r /opt/local/share/swig/*/std to <mygrsource>/gnuradio-core/src/lib/swig cat of : patch-path-order.diff patch-volk_lib_CMakeLists.txt.legacy.diff patch-volk_gen_archs.xml.legacy.diff patch-gnuradio-core_swig_std_std_container.i.diff patch-gnuradio-core_swig_include-std_string.i.diff then apply resulting patch, then build as usual NEW releases (3.7 and above) cp -r /opt/local/share/swig/*/std to <mygrsource>/gnuradio-runtime/src/lib/swig cat of : patch-gnuradio-runtime_swig_std_std_container.i.diff patch-gnuradio-runtime_swig_include-std_string.i.diff then apply resulting patch, then build as usual Have I nailed it or not yet ? Let me know. Regards, ARturo |
[Prev in Thread] | Current Thread | [Next in Thread] |