[yocto] Build only one specific C source from git clone with many C files
Hi, I want to build only spidev_test.c from kernel sources (kernel/Documentation/spi/spidev_test.c) Is it possible to modify SRC_URI to take only one source file from a git clone and build it? Any inputs will be of help! Regards, Pj -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Is it possible NOT to split kernel modules in multiple packages
On Fri, Jan 27, 2017 at 7:18 AM, Khem Raj <raj.k...@gmail.com> wrote: > > > On 1/25/17 11:29 PM, Prasant J wrote: >> Hi, >> >> I'm using Morty release to create my custom BSP package for cortex-a5 >> based processor. >> >> I'm using my own custom kernel recipe that inherits kernel.bbclass >> (which inherits kernel-module-split.bbclass) >> >> >> All the modules are split in their own rpm packages. Is it possible >> that only one RPM package is created for all kernel modules and there >> is no split? >> > > I guess you want to include all the modules into your image. In that > case you can add > > MACHINE_EXTRA_RRECOMMENDS += "kernel-modules" > > in your machine config. > @ Khem: Thanks for response! Yes, I want to include all modules. ALSO (more importantly) I want only one RPM for all modules. Instead of 50 or more rpms I would like to have only 1 rpm which has all the kernel modules. Is it possible? The reason I want this: I have my own GUI for system package management for our end-users. I want to make it simple for them to install newer modules by installing only 1 rpm. Regards, Pj -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] Is it possible NOT to split kernel modules in multiple packages
Hi, I'm using Morty release to create my custom BSP package for cortex-a5 based processor. I'm using my own custom kernel recipe that inherits kernel.bbclass (which inherits kernel-module-split.bbclass) All the modules are split in their own rpm packages. Is it possible that only one RPM package is created for all kernel modules and there is no split? Regards, Pj -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] smartpm: is there a checksum verification for rpm downloads?
Hi, I'm using Smart + RPM for package management on my embedded linux systems. We are currently using scripts for checksum verification of downloaded rpm packages. Does smart have an inbuilt facility to verify md5 or sha256 of rpm packages downloaded from server? Regards, Prasant -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] RPM Packaging
Hi, I want to create custom rpm packages for the iMX6Q device (cortexa9hf-vfp-neon-mx6). I have to create two types of packages: either pre-built arm binaries to be packed or packages containing only bash scripts. There is no need of cross-compiling while packaging for my cases. I'm building the packages on my Ubuntu system. When I specify - BuildArch: cortexa9hf-vfp-neon-mx6, and try to create a package (rpmbuild -ba SPECS/foo.spec), it complains error: No compatible architectures found for build. For my case: rpm does not need to cross-compile but just do the packaging. How can I force rpm to believe the architecture that I'm specifying? Any inputs will be of help. Regards, Pj -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Embedded Linux Package Management
On Fri, Mar 20, 2015 at 4:44 PM, Paul Eggleton paul.eggle...@linux.intel.com wrote: On Friday 20 March 2015 11:10:39 Paul Eggleton wrote: On Friday 20 March 2015 11:26:43 Alex J Lennon wrote: On 20/03/2015 11:15, Prasant J wrote: On Fri, Mar 20, 2015 at 2:21 PM, Alex J Lennon I don't know. To me the question would be does it do want I need it to do as well as I need it to do it, rather than asking whether there is a lot of activity. One might take the view that if it is doing its job, a lack of activity is a sign that it's a mature piece of software that needs little further development. You'll have to make that decision yourself. My understanding is that smart is the recommended way to do things (at least it was what was recommended to me) - https://wiki.yoctoproject.org/wiki/Smart @Alex: You are correct, it should be able to do what I need. It did most of the things that I need. But I'm not fine in using a package if the development has stopped. Smart may stop development but other packages continue to develop. It is important for me to know that the maintainer will continue to provide compliance as other libraries are actively developed. FYI, here is some of the thinking that led to the decision to use smart: https://lists.yoctoproject.org/pipermail/yocto/2012-October/010384.html Of course that was a few years ago now - we probably ought to look at the RPM landscape again (e.g. DNF) and see if any change is warranted. @Paul: This is a very important link for me. This posts points out that yum will not be compatible with rpm ver 5. This will be a problem for me as my imx6 yocto build uses rpm5. So technically I cannot use yum. I forgot to mention, we do have some basic documentation here on setting up a feed if you hadn't already seen it: http://www.yoctoproject.org/docs/current/dev-manual/dev-manual.html#using-runtime-package-management Thanks for inputs. Would like to get more inputs from community. Looks like Alex is successful and happy in using smart + rpm. I would re-consider smart + rpm for my solution. Anyone else using any other package management solution ? Regards, Pj -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Embedded Linux Package Management
On Fri, Mar 20, 2015 at 2:21 PM, Alex J Lennon ajlen...@dynamicdevices.co.uk wrote: On 20/03/2015 09:34, Prasant J wrote: Hi, I'm looking for package management for my embedded linux systems (yocto on armv7 iMX6Q) I'm looking for the following features: (a) Install remove a package (b) Install packages and its dependencies (c) Install a package with conflicts, such that the conflicting package is force removed (d) A local location with packages should serve as a package source (e) Remote server package (http file server based) (f) List of my packages installed (g) List of my packages not installed but available on the http file server (h) List of my packages that have updates (new version) (i) To be able to manage packages for multiple architectures (eg. rpm can produce packages for multiple architectures using one spec file) The above features will be invoked by the application GUI. Any suggestions: which package management solution would answer all the above use cases? (e) I use smart + RPM. I have a remote package server setup via this in local.conf FEED_DEPLOYDIR_BASE_URI = http://packages.foo.bar; Then I'm rsyncing the files up to the server after a bitbake package-index. Then smart update / search / install That seems to work well in my testing. Hi Alex, Thanks for inputs! Is smart development stopped? When I look at their mailing list it, the last posts were in Nov 2014. It looks like no more development for smart package manager. I would then tend to say that it will not be a right way for me. Regards, Pj -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] Embedded Linux Package Management
Hi, I'm looking for package management for my embedded linux systems (yocto on armv7 iMX6Q) I'm looking for the following features: (a) Install remove a package (b) Install packages and its dependencies (c) Install a package with conflicts, such that the conflicting package is force removed (d) A local location with packages should serve as a package source (e) Remote server package (http file server based) (f) List of my packages installed (g) List of my packages not installed but available on the http file server (h) List of my packages that have updates (new version) (i) To be able to manage packages for multiple architectures (eg. rpm can produce packages for multiple architectures using one spec file) The above features will be invoked by the application GUI. Any suggestions: which package management solution would answer all the above use cases? I have tried smart + rpm, but from my preliminary research suggests that smart is no longer developed (Am I correct?). Also I failed to setup remote repository [case (e)] and also case (h) failed. I am currently trying out yum + rpm, but it fails to answer case (f). It can lists all my packages but does not tell me if it is installed or available on the repo. I could make it work by additional steps (work around), but it will be good if the tool itself supports these features. It also fails case (c), does not force remove conflicting package. I also looked at opkg, but the last stable release seems to be v0.2.4 (v0.3.0-rc2 is current). Is it mature enough to be used? Does ipk packages support all features as rpm packages would support (dependencies, conflicts, groups) ? Sorry for asking a lot of questions. It would be very helpful if someone who has worked with package management on linux systems can give some inputs. Thanks in advance! Regards, Pj -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
