This is merely a historical archive of years 2008-2021, before the migration to mailman3.
A maintained and still updated list archive can be found at https://lists.osmocom.org/hyperkitty/list/baseband-devel@lists.osmocom.org/.
Bhaskar11 niceguy108 at gmail.comShould we consider separating *only* the shared header definitions and APIs into a separate "shared" folder which would be accessed by the ARM compiler and host compilers from *all* Osmocom related projects? I've been porting the code to Windows and can see the benefits of clear separation of code. B. On Mon, Jan 21, 2013 at 5:39 PM, Harald Welte <laforge at gnumonks.org> wrote: > On Mon, Jan 21, 2013 at 10:51:53AM +0100, Sylvain Munaut wrote: > > The host build was becoming a problem and that's why it was moved out. > > The target build has not caused issue so I don't see why we would > > change it and give it the opportunity to fail. > > btw, just for the record: the idea of the host build from inside > osmocom-bb.git was to make sure that the header files and APIs on both > sides would be identical, which was considered a helpful idea if more > and more code is eventually moved from host into the target (which never > happened so far). > > -- > - Harald Welte <laforge at gnumonks.org> > http://laforge.gnumonks.org/ > > ============================================================================ > "Privacy in residential applications is a desirable marketing option." > (ETSI EN 300 175-7 Ch. > A6) > > -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.osmocom.org/pipermail/baseband-devel/attachments/20130124/3abcae42/attachment.htm>