On Sat, Jan 18, 2014 at 9:48 AM, Marcus Müller <mar...@hostalia.de> wrote:
> -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > Hi Niklos, > > you're on a wrong track; when I had my first contact with GR, the > project was still using Autoconfigure/Automake for building. CMakeList > ist part of the CMake-based build system that GR adapted later on in the > 3.4 development process (if I remember correctly). > > And that's exactly where your problems start: That build system was > complicated, and not very flexible. Thus, it's not very easy to fix > dependencies if for example libraries used by GR changed their file > naming structure etc. > This wouldn't be a big problem if there would only have been a very few > changes in the open source software world; but remember, we are talking > about the world of 2006! So in order to get GR to compile you not only > have to get the right source code version of GR, you need to get the > correct development and built version of all the required libraries to > be *available* for your system. This is not very likely to be the case > anymore! Lots of things simply have changed since then - possibly > including not only libraries, but hard-to-tame things like autoconfigure > too. > > To put summarize your options: > If the 2006 legacy application code is complicated, large and of high > importance to eg test the functionality, then set up a VM running a > Debian from back-in-the-days and try to build and run your application > there. Obviously, as you seem to be hesitant to port the application to > a modern GR (and from an application point of view, this is equal to not > porting it to a halfway-recent operation system) it will be > unmaintainable; and that is a bad thing (tm). > > If you just want to understand what's happening inside your legacy > application, well, it might be easier to just read the source code (and > maybe port it to 3.7.2 in the process, which is easier than you might > expect due to tools that ease the pain of having to write a lot of > boilerplate code). > > If your business / research really depends on that legacy code: > Get the source code. You *must* be able to get it from your supplier, > otherwise as Marcus (the other Marcus) already said, he'd be in a bit of > a legal problem. And as said before, since if it is critical to you, > you'll need to future-proof it by porting it to GR 3.7. > > Greetings, > Marcus > > Hi Marcus, Thnx for the advise. I will have to try. Maybe I will prove wrong. I will know within the next week. I am an opensource guru, having contribute to several projects, and am aware of the license limitations. 2.8 is more recent than 2006. 2006 is the earliest year in the repository. I have tried building the earliest revision in your repository, and it did fine, until it failed due to a missing "Makefile.in" file. No failed library dependencies, since most software checks for versions >= a given level. It is a good thing that opensource is mostly backwards-compatible ;-) As I mentioned to the other Marcus, that's my ultimate goal. I need the 2.8 version to understand better both gnuradio and the other application. Then I will write my code for the final product. My product is classified, so i am sorry if I cannot be more open with it. My clients are the police and the military. I would like to thank each one in this group. Not only there was a huge response for an outdated version, well OK, just for finding it, but also while I asked for onoy 1 of 2 options in locating it, I was offered both ;-) Please hear my advise. Developers should support the "gnuradio -v" option and use an include file to do it. In a few years git will be superseded by another versioning system. The only way to ensure that versions are preserved across any such migration, is to have it embedded in the sources ;-) ty Nikos On 18.01.2014 07:53, Nikos Balkanas wrote: > > On Sat, Jan 18, 2014 at 12:05 AM, Tom Rondeau <t...@trondeau.com> > > wrote: > > > >> On Fri, Jan 17, 2014 at 1:30 PM, Nikos Balkanas > >> <nikos.balka...@eyeonix.com> wrote: > >>> > >>> I am trying to get from the repository gnuradio v 2.8. Since I > >>> don't know dates or revision numbers, I download revisions and > >>> check them out. > >>> > >>> I have an either or question. Does anyone know of a stable 2.8 > >>> revision > >> for > >>> me to download? Failing that, i would appreciate it if someone > >>> could > >> tell me > >>> a way to get gnuradio's version # from the source tree (without > >>> building it). > >>> > >>> TIA, Nikos > >> > >> I think you might be confused. You don't really mean 2.8, do you? > >> I would imagine you're looking for 3.8, which doesn't actually > >> exist yet. We're currently on 3.7.2.1. > >> > >> You can look in git for the version releases by using "git tag" > >> to see a list of tags that correspond to the version. Wen you > >> have a version of GNU Radio, you can look at the root > >> CMakeLists.txt file for the "VERSiON_INFO_MAJOR_VERSION" and > >> other version variables set up here. > >> > >> Tom > >> > > > > I have grepped through all sources, but didn't check CMakeLists. > > This might just do it. Thanks ;-) > > > > > > > > _______________________________________________ Discuss-gnuradio > > mailing list Discuss-gnuradio@gnu.org > > https://lists.gnu.org/mailman/listinfo/discuss-gnuradio > > > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1 > Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ > > iQEcBAEBAgAGBQJS2jGwAAoJEAFxB7BbsDrLUK8IAIegjKtJJVSnMJy4jFxJB7N5 > C7Hs01skGoJiDz83c4aJAL6SF0ozEp2kn2wsToUMPWQ2kARudM8Mfb6VVke9QTg3 > Ur/ztpSKNtGAZufQYNOE7FQgX9HeGMuHVgLP0c4LOpDPU9VA9jeiV0NESHfoi6aC > eU0wXdH+mlTgWhmQElLBQzwfo5m3mq29RHFAvQYKC1kue7JF5jKzHbD6KP7f+Ukj > bEMUb6cgb1k2kqL+6KgShzc1NfCzOb0BF89HAp9lXIH79zKDYudENvGgFU/Z8O+N > vWanreBeXnyGMNaPPZ276luzGiu0caufQfSno9GvrISlhuFJJORfJOTEjxlwuqw= > =gbX4 > -----END PGP SIGNATURE----- > > _______________________________________________ > Discuss-gnuradio mailing list > Discuss-gnuradio@gnu.org > https://lists.gnu.org/mailman/listinfo/discuss-gnuradio >
_______________________________________________ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
