Summary: | ModemManager porting to Embedded System | ||
---|---|---|---|
Product: | ModemManager | Reporter: | msong <songmin1948> |
Component: | general | Assignee: | ModemManager bug user <modemmanager> |
Status: | RESOLVED NOTABUG | QA Contact: | |
Severity: | enhancement | ||
Priority: | medium | ||
Version: | unspecified | ||
Hardware: | ARM | ||
OS: | Linux (All) | ||
Whiteboard: | |||
i915 platform: | i915 features: |
Description
msong
2016-09-26 12:24:54 UTC
Really depends on the system you're targeting and how packages are usually built there. There is no 'porting' really needed for the specs you say, just a proper toolchain and the correct configure options; e.g. an example could be (likely not exactly what you need): $ PKG_CONFIG_PATH=/opt/toolchain/lib/pkgconfig/ ./configure --host=armv7l-linux-gnueabi --prefix=/opt/toolchain/ CC=/opt/toolchain/bin/armv7l-linux-gnueabi-gcc $ make $ sudo make install So, you'll need to see what your target system requires and pass the correct configure flags. Will close this bugreport as it's not really a bug. Please refer to the ModemManager mailing list for this kind of questions :) https://lists.freedesktop.org/mailman/listinfo/modemmanager-devel |
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.