Build a binary package without SDK?

ttc0419 · March 1, 2023, 4:17am

Hi, I'm trying to package a binary program. It does not need to be compiled. Is there a simpler way to create ipk without setting up the SDK environment? I tried to use opkg-build script from opkg-utils. However, when I install the ipk, it shows

Collected errors:
 * pkg_init_from_file: Malformed package file p.ipk.

I find out that the file type is different, openwrt ipk:

[uuu@hhh ddd]% file adb-enablemodem_2017-03-05-1_aarch64_cortex-a53.ipk
adb-enablemodem_2017-03-05-1_aarch64_cortex-a53.ipk: gzip compressed data, from Unix, original size modulo 2^32 10240

ipk created by opkg-build:

[uuu@hhh ddd]% file p.ipk 
p.ipk: Debian binary package (format 2.0), with control.tar.gz, data compression gz

ttc0419 · March 1, 2023, 2:19am

Hi, I'm trying to package a binary program, the developers provides the programs for multiple targets.. Is it possible to write a Makefile to create multiple ipks for different targets? Are there any examples for this? Thanks.

psherman · March 1, 2023, 7:10am

MODERATOR NOTE: These two posts appear to be very closely related. To ensure that the answers don't become bifrucated between two or more threads, I have merged them into this one.

olitoutlemonde · April 11, 2024, 9:15am

Hello,
I had the same issue using the opkg-build tool from this repo:

github.com

shr-project/opkg-utils/blob/master/opkg-build

#!/bin/sh

# opkg-build -- construct a .opk from a directory
# Carl Worth <cworth@east.isi.edu>
# based on a script by Steve Redler IV, steve@sr-tech.com 5-21-2001
# 2003-04-25 rea@sr.unh.edu
#   Updated to work on Familiar Pre0.7rc1, with busybox tar.
#   Note it Requires: binutils-ar (since the busybox ar can't create)
#   For UID debugging it needs a better "find".
set -e

version=1.0

opkg_extract_value() {
	sed -e "s/^[^:]*:[[:space:]]*//"
}

required_field() {
	field=$1

This file has been truncated. show original

after running the command opkg-build , you get the ipk file. Here is what you need to do then:

ar x <malformed package>.ipk
tar czf <proper package>.ipk control.tar.gz data.tar.gz debian-binary

You can then test the file type:

# file adguardhome-wrapper_1.0-1_all_new.ipk
<proper package>.ipk: gzip compressed data, from Unix, original size modulo 2^32 10240

You can then install your ipk file. I tested that to force some postinst operations after installing a package and that worked fine

olitoutlemonde · April 11, 2024, 9:46am

ok, looking at the official yocto project git repo, there is a more "built in" way of doing.
https://git.yoctoproject.org/opkg-utils/

Based on the opkg-build tool available with the above link, you need to use the "-c" option to build your package:

opkg-build -c <folder name>

This forces the use of tar instead of ar to build the package