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 ?
Related
I'm trying to generate an apk for my react pwa, its says unable to load the "svg2img" library. SVGS are not supported, I do think that this is a third-party library used by one of my installed libraries. Is there a work around for this?
I created a native OCR module using N-API (node-addon-api) with bindings to tesseract OCR.
My intention is to get native OCR working under electron. I basically checked all the npm packages related to OCR and they all don't work with electron. And here is my own test project
based on electron, which uses my node-native-ocr module:
https://github.com/stoefln/electron-ocr
My problem:
I don't manage to package all the dependencies when bundling electron. Or there seems to be a problem with the way I do it, because I am currently getting this error when running the electron project in production:
dyld: Symbol not found: _fmemopen Referenced from: /Volumes/Shared
Folders/Downloads/Electron
OCR.app/Contents/Resources/app/node_modules/node-native-ocr/build/Release/dependencies/liblept.5.dylib
Expected in: /usr/lib/libSystem.B.dylib
The way I am currently trying to package: The .node file which is generated depends on tesseract (built with brew) which depends on a lot of other libraries installed on the system.
What I came up with is a script which recursively reads dependencies (otool -l), copies them into the .node folder and changes the link (install_name_tool -change ...) to point to the copied dylib file.
I am not even sure if that's the right way of doing it. Shouldn't the node-gyp linker take care of linking AND packaging everything?
Here is somebody asking basically the same question: https://github.com/nodejs/node-gyp/issues/2258
More information if you want to reproduce my problem:
Run npm run export-mac
Copy the .app file to some other machine, to make sure it does not use the libararies in the system and only the ones which are packaged.
Start the app via the command line (otherwise you won't see the error): ./your_path_to_the_app_file/Electron\ OCR.app/Contents/MacOS/Electron\ OCR
Click the single button in the UI and check the terminal output
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 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.
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.