Forums » Software Development »
Building new openembedded-core based system from scratch
Added by Thomas Catalino over 12 years ago
(posted on behalf of a customer)
I would like to build a dev environment from scratch if possible and am following the beta instructions for building the new openembedded-core based system
The build is failing because of a reference to a base URI of a subversion repository svn://wanda/svn/mityomap/mityomapl138 in file sources/meta-mitydsp/include/mitydsp-preferred-revs.inc
It looks like an internal repository on your "wanda" machine. Is there an equivalent external URI I could use to access this repository?
Replies (4)
RE: Building new openembedded-core based system from scratch - Added by Michael Williamson over 12 years ago
At the moment, we cannot expose the full repository as there is proprietary data stored in it.
We need to work with our team to sort out how to either push a cloned repository with the bits of proprietary data removed or periodically push a tarball out that could be used in lieu of a repository.
Technically, you may be able to build your dev environment without our repository. The meta-toolchain-qte, for example, should build cleanly without our repository. The only information that is really sourced from there are the FPGA drivers, DSPLINK, and a couple of miscellaneous libraries (libdsp, libdaq). The kernel and u-boot are already available on this support site. All of the source code for these items is available in snapshot form within the board support / MDK releases (and the DSPLINK is actually downloadable from TI).
Sorry for the inconvenience. As soon as we sort this out I will provide a follow up post, though you'll likely see updates to the meta layer repository when we are able to reference an external server for whatever value add code we include in OE recipe form.
-Mike
RE: Building new openembedded-core based system from scratch - Added by Andrea Galbusera over 12 years ago
Hi,
I'm new to the MityDSP world, but me too, highly interested in this topic.
Could you please clarify if the proprietary bits you are talking about are somewhat related to what meta-mitydsp is supposed to provide to openembedded users?
My main concern is under what license the FPGA drivers are made available. According to recipes-bsp/fpga-drivers/fpga-driver-modules.bb in meta-mitydsp they should be under the GPLv2, could you please confirm?
If I understand correctly by grepping for 'LICENSE=' under meta-mitydsp, all components provided by this layer should be available under some free license. Am I missing something?
Any idea how long will it take to have public access to the missing sources? In the meanwhile I'll reference the snapshots sources...
Regards,
Andrea
RE: Building new openembedded-core based system from scratch - Added by Michael Williamson over 12 years ago
To clarify (hopefully):
None of our software that is part of the MityDSP-L138 development kit is proprietary. The only things that we keep proprietary in our MityDSP-L138 releases are:
- FPGA VHDL source code for our "cores" (netlists are available, though, and you can use them for your projects).
- The hardware design files for the modules (schematics, layout data, etc.). Data for the devkit boards is available.
The FPGA linux kernel drivers are required to be GPL'd as they are linked in against the kernel (we do not attempt to wrap them).
The issue we have is that we have one subversion repository that includes all critical link developed software (the linux and u-boot stuff is separate in the shared git trees) as well as the hardware design files. Someone needs to either separate them or we need to make regular tarballs and push them to an external server for the bitbake recipes to grab. It's "on the list" but resources are a bit stretched right now.
I'm very sorry for the inconvenience.
-Mike
Building openembedded-core from scratch : MityDSP overlay breaks meta-toolchain-qte - Added by Phil Sanderson about 12 years ago
Hi,
Is there a fix yet for the broken build system?
Would it not be possible to move the open parts to a public repository?
Thanks
Phil