I need to modify Shamu msm kernel to enable loading of driver modules.
When i try using the below flags in shamu_defconfig, I get build errors.
CONFIG_MODULES=y
Is there any dependency for enabled module load in Shamu kernel ?
You need to use make menuconfig command to enable loadable modules. It will follow all required dependencies for you.
Related
Our project comprises multiple modules. One of the plugins we use (soapui-maven-plugin used to provide mock services) needs a different configuration for each module.
That particular plugin, however, apparently does not end and get restarted for each module but "survives" between the modules. I.e. the first instance continues to run while subsequent modules are being built. The problem is, that this instance is then wrongly configured for those subsequent modules and hence out unit-test fail.
The plugin does not provide any explicit "stop" goal or such to explicitly terminate it.
My question thus: is there a generic way that would allow to enforce that all (or a specific) plugin(s) started for the build of a module is terminated at the end of the build of that module? Such that the subsequent build of a successor module then needs to restart that module again (using the proper config for that next module).
I would have expected that this is the default behavior of Maven and its plugins to terminate after each module but obviously not so. Is that maybe some artifact of enabling parallel builds?
Or can one force that plugin termination somehow?
For some debug purpose I am trying to get android inbuild/static drivers description in device like modinfo for loadable modules.
but modinfo is not working for non ".ko" modules.
Is there any similar way to get description of inbuild/static kernel modules ?
I have an AngularJS application that I'm having dependency injection issues with. Essentially, the application module conf contains two submodules core and conf.mods which are both dependencies on conf.
core has a core.components dependent module, which has a MenuProvider provider defined on it. conf.mods has a dependent module conf.mods.dash which has a config block that needs to inject MenuProvider. When everything loads up, I get an "Unknown Provider" error on the conf.mods.dash config block, even when I try to set core or core.components as a dependency on conf.mods.dash.
The source code is in a github here
What's curious is that the MenuProvider is available during the run block of conf.mods.dash, which I guess makes sense. How can I get MenuProvider to be available during the config block of conf.mods.dash?
If you pull the source, run npm install, bower install and gulp to start the file watch.
I am trying to build PNaCl for use in CEF. I have managed to build the PPAPI examples as defined here:
1. Build CEF3/Chromium from source code as described at https://code.google.com/p/chromiumembed ... ndBuilding.
2. Edit C:\chromium\src\build\some.gyp, add '../ppapi/ppapi_internal.gyp:ppapi_example_paint_manager' in the 'dependencies' section.
3. Run `gclient runhooks` from the chromium src directory to update the build files.
4. Open C:\chromium\src\build\some.sln (on equivalent on other platforms) and build the ppapi_example_paint_manager target to create ppapi_example_paint_manager.dll.
How do i configure gyp for building a PNaCL/NaCl plugin that i can load into CEF?
Loading a NaCl or PNaCl plugin into CEF will be no different than loading it into Chrome. As such, you can use the standard build tools for building Native Client plugins. Start with the Native Client SDK, and try building the demos and examples there.
You won't typically use gyp for building PNaCl/NaCl plugins. Using gyp is difficult because it requires manually setting up the Native Client toolchains as the build target. The Native Client SDK includes a set of Makefiles that do this for you automatically.
You may also want to take a look at naclports. This repository has ports of many open-source libraries to Native Client, which may help you in porting your application.
I have downloaded and extracted libraries API as it is
sites/all/libraries
but seems not working my dependency library PHPExcel. Any suggestion?
Did you download and enable the libraries module also? This module has to be installed under "sites/all/modules" folder (according to your setup).
Inside "sites/all/libraries" you have to put the library (PHPExcel) not the module.