23 Apr
2016
23 Apr
'16
6:35 p.m.
Hi all,
There has been a few questions recently about building
OpenBSC/OsmoBTS, especially for SDR devices, so I decided to share a
link to a "make world" style build script which may help newcomers to
get started.
The script was hacked together by Sergey Kostanbaev to build static
binaries and was not meant for wide use, so it have rough edges and
may not work for every setup, but I hope it'll be useful for someone.
Check out this git repository for the source code and brief documentation:
https://github.com/fairwaves/osmo-combo
--
Regards,
Alexander Chemeris.
CEO, Fairwaves, Inc.
https://fairwaves.co
26 Apr
26 Apr
2:04 p.m.
On Sat, Apr 23, 2016 at 06:35:42PM +0200, Alexander Chemeris wrote:
Hi all,
There has been a few questions recently about building
OpenBSC/OsmoBTS, especially for SDR devices, so I decided to share a
link to a "make world" style build script which may help newcomers to
get started.
The script was hacked together by Sergey Kostanbaev to build static
binaries and was not meant for wide use, so it have rough edges and
may not work for every setup, but I hope it'll be useful for someone.
Check out this git repository for the source code and brief documentation:
https://github.com/fairwaves/osmo-combo
Nice, thanks!
I do have a build-all shell script for the 3G stack that I heavily use to
ensure clean builds. Maybe I can translate it into a Makefile like this
one...
But, hold on, are you actually mirroring the osmo* source trees in that
repository? Makes it kind of hard to contribute back to upstream, right?
I'd prefer to have just the Makefile, which (as a rainbow unicorn) could
also clone the git sources if not present...
Anyway, thanks for sharing!
~Neels
--
- Neels Hofmeyr <nhofmeyr(a)sysmocom.de> http://www.sysmocom.de/
=======================================================================
* sysmocom - systems for mobile communications GmbH
* Alt-Moabit 93
* 10559 Berlin, Germany
* Sitz / Registered office: Berlin, HRB 134158 B
* Geschäftsführer / Managing Directors: Holger Freyther, Harald Welte
9:27 p.m.
On Apr 26, 2016 2:04 PM, "Neels Hofmeyr" <nhofmeyr(a)sysmocom.de> wrote:
On Sat, Apr 23, 2016 at 06:35:42PM +0200, Alexander Chemeris wrote:
But, hold on, are you actually mirroring the osmo* source trees in that
repository? Makes it kind of hard to contribute back to upstream, right?
I'd prefer to have just the Makefile, which (as a rainbow unicorn) could
also clone the git sources if not present...
Not sure you can call it a unicorn, may be rather a gnucorn..
This script is using git submodules to "symlink" all dependencies. So
subdirectories look like normal git repos and you can work with them
individually, as well as perform batch operations.
You can google details, but here are a couple links which come up on the
top of my google search and have relevant information:
https://chrisjean.com/git-submodules-adding-using-removing-and-updating/
http://stackoverflow.com/questions/5542910/how-do-i-commit-changes-in-a-git…
--
Regards,
Alexander Chemeris
CEO Fairwaves, Inc.
https://fairwaves.co
27 Apr
27 Apr
7:10 p.m.
hello,
What is the Linux distribution that you advocated for this script ?
Thank you for the great job.
2016-04-26 21:27 GMT+02:00 Alexander Chemeris <alexander.chemeris(a)gmail.com>
:
On Apr 26, 2016 2:04 PM, "Neels Hofmeyr" <nhofmeyr(a)sysmocom.de> wrote:
On Sat, Apr 23, 2016 at 06:35:42PM +0200, Alexander Chemeris wrote:
But, hold on, are you actually mirroring the osmo* source trees in that
repository? Makes it kind of hard to contribute back to upstream, right?
I'd prefer to have just the Makefile, which (as a rainbow unicorn) could
also clone the git sources if not present...
Not sure you can call it a unicorn, may be rather a gnucorn..
This script is using git submodules to "symlink" all dependencies. So
subdirectories look like normal git repos and you can work with them
individually, as well as perform batch operations.
You can google details, but here are a couple links which come up on the
top of my google search and have relevant information:
https://chrisjean.com/git-submodules-adding-using-removing-and-updating/
http://stackoverflow.com/questions/5542910/how-do-i-commit-changes-in-a-git…
--
Regards,
Alexander Chemeris
CEO Fairwaves, Inc.
https://fairwaves.co
7:30 p.m.
On Apr 27, 2016 20:10, "Choukou Moun" <choukoumoun(a)gmail.com> wrote:
What is the Linux distribution that you advocated for this script ?
I don't think it matters for the build script, but we've been testing it
under Ubuntu 14.04 64-bit
--
Regards,
Alexander Chemeris
CEO Fairwaves, Inc.
https://fairwaves.co
9:16 p.m.
Ok.
But i think your script doesn't install UHD and UMTRX/UHD lib and driver ?
2016-04-27 19:30 GMT+02:00 Alexander Chemeris <alexander.chemeris(a)gmail.com>
:
On Apr 27, 2016 20:10, "Choukou Moun" <choukoumoun(a)gmail.com> wrote:
What is the Linux distribution that you advocated for this script ?
I don't think it matters for the build script, but we've been testing it
under Ubuntu 14.04 64-bit
--
Regards,
Alexander Chemeris
CEO Fairwaves, Inc.
https://fairwaves.co
10:24 p.m.
Its work Thank you
Le 27 avr. 2016 21:16, "Choukou Moun" <choukoumoun(a)gmail.com> a écrit :
Ok.
But i think your script doesn't install UHD and UMTRX/UHD lib and driver ?
2016-04-27 19:30 GMT+02:00 Alexander Chemeris <
alexander.chemeris(a)gmail.com>gt;:
On Apr 27, 2016 20:10, "Choukou Moun" <choukoumoun(a)gmail.com> wrote:
What is the Linux distribution that you advocated for this script ?
I don't think it matters for the build script, but we've been testing it
under Ubuntu 14.04 64-bit
--
Regards,
Alexander Chemeris
CEO Fairwaves, Inc.
https://fairwaves.co
10:30 p.m.
On Wed, Apr 27, 2016 at 10:16 PM, Choukou Moun <choukoumoun(a)gmail.com> wrote:
But i think your script doesn't install UHD and
UMTRX/UHD lib and driver ?
The script doesn't install any dependencies - it only build Osmocom
part of things. This is mentioned in the README.
--
Regards,
Alexander Chemeris.
CEO, Fairwaves, Inc.
https://fairwaves.co
28 Apr
28 Apr
1:43 p.m.
On Tue, Apr 26, 2016 at 09:27:36PM +0200, Alexander Chemeris wrote:
On Apr 26, 2016 2:04 PM, "Neels Hofmeyr"
<nhofmeyr(a)sysmocom.de> wrote:
LOL, a gnunicorn :)
On Sat, Apr 23, 2016 at 06:35:42PM +0200, Alexander Chemeris wrote:
But, hold on, are you actually mirroring the osmo* source trees in that
repository? Makes it kind of hard to contribute back to upstream, right?
I'd prefer to have just the Makefile, which (as a rainbow unicorn) could
also clone the git sources if not present...
Not sure you can call it a unicorn, may be rather a gnucorn.. This script is using git submodules to
"symlink" all dependencies. So
ah of course, thanks. In github's tree listing it's easy to assume that
they are copies of the original git sources, but now I noticed the
.gitmodules file...
...and I see that libosmocore and openbsc are in fact included from the
fairwaves github repositories. I think this is worth a mention in the
README file. I'll post a pull request when I get around to it...
Thanks!
~Neels
2:57 p.m.
New subject: proliferation of repositories + branches (Re: osmo-combo build script)
An unrelated note:
On Thu, Apr 28, 2016 at 01:43:54PM +0200, Neels Hofmeyr wrote:
...and I see that libosmocore and openbsc are in fact
included from the
fairwaves github repositories.
Can we please work together to skip further proliferation of branches,
let alone repositories? This really troubles me.
fairwaves have full commit access to the respective projects on
git.osmocom.org, so I don't really think it is wise to further
proliferate different repositories.
The work should be focussed on merging and unifying the codebase, rather
than further forking and confusing every single user and developer.
We need one version of the code that works for everyone, particularly
for core components like the libraries.
Thanks for your attention.
Regards,
Harald
--
- Harald Welte <laforge(a)gnumonks.org> http://laforge.gnumonks.org/
============================================================================
"Privacy in residential applications is a desirable marketing option."
(ETSI EN 300 175-7 Ch. A6)
10:31 p.m.
New subject: proliferation of repositories + branches (Re: osmo-combo build script)
Hi Harald,
On Thu, Apr 28, 2016 at 3:57 PM, Harald Welte <laforge(a)gnumonks.org> wrote:
On Thu, Apr 28, 2016 at 01:43:54PM +0200, Neels
Hofmeyr wrote:
I was actually going to write that the only reason for this is
historical. Sergey didn't have commit access originally and was doing
development in our github clone. Now that he has commit access and
branches are pushed to git.osmocom.org, there is no real reason to
point to our github. I've updated the .gitmodules to point to
git.osmocom.org.
...and I see that libosmocore and openbsc are in
fact included from the
fairwaves github repositories.
fairwaves have full commit access to the respective projects on
git.osmocom.org, so I don't really think it is wise to further
proliferate different repositories. The work should be focussed on merging and unifying
the codebase, rather
than further forking and confusing every single user and developer.
We need one version of the code that works for everyone, particularly
for core components like the libraries.
I'm totally with you on this.
--
Regards,
Alexander Chemeris.
CEO, Fairwaves, Inc.
https://fairwaves.co
10:47 p.m.
New subject: proliferation of repositories + branches (Re: osmo-combo build script)
On Thu, Apr 28, 2016 at 11:31:12PM +0300, Alexander Chemeris wrote:
I've updated the .gitmodules to point to
git.osmocom.org.
thanks.
I'm totally with you on this.
thanks, too.
In terms of branches: What would also be useful is some consolidated
overview about what kind of bugs/features/... are missing in master from
the fairwave point of view, i.e. what prevents you from using master for
each project where you're not using master.
Regards,
Harald
--
- Harald Welte <laforge(a)gnumonks.org> http://laforge.gnumonks.org/
============================================================================
"Privacy in residential applications is a desirable marketing option."
(ETSI EN 300 175-7 Ch. A6)
29 Apr
29 Apr
9:12 a.m.
New subject: proliferation of repositories + branches (Re: osmo-combo build script)
On Apr 29, 2016 9:15 AM, "Harald Welte" <laforge(a)gnumonks.org> wrote:
On Thu, Apr 28, 2016 at 11:31:12PM +0300, Alexander Chemeris wrote:
In terms of branches: What would also be useful is some consolidated
overview about what kind of bugs/features/... are missing in master from
the fairwave point of view, i.e. what prevents you from using master for
each project where you're not using master.
That is a good idea. Let me look into what we have on our branches.
--
Regards,
Alexander Chemeris
CEO Fairwaves, Inc.
https://fairwaves.co
3344
days inactive
3350
days old
12 comments
4 participants
participants (4)
-
Alexander Chemeris -
Choukou Moun -
Harald Welte -
Neels Hofmeyr