Am I allowed to pay a member for a community build?

Is it allowed to offer to pay another member to compile a custom community build? Or is that against terms of service here?

1 Like

Turns out I don't need to shortcut this by asking/paying for someone to compile an image. I figured it out myself. Compiling images for ASUS and TP-Link OnHub.

Just got one warning during the compile process:

WARNING: Makefile 'package/kernel/mac80211/Makefile' has a dependency on 'kmod-qca-nss-drv', which does not exist

Is this going to be a problem if I flash the image?

Most likely.

In the context of what you’re trying to accomplish, that’s the mother of all problems.

Hoping @Kong or @ACwifidude sees this and helps me workaround the issue. I’m thinking the file that does not exist is compiled later in the compile process and the warning was triggered, but it had not been compiled yet.

1 Like

Put an @ in front of their username to invite them...

e.g. @KSofen

1 Like

To answer this question (since it hasn't yet been addressed):

This forum is staffed by volunteers and in general these forums aren't really a place where we discuss payment for normal help. As such, each member/contributor will choose to engage on topics based on their own desire and ability to help. In some cases, a thread may gain zero traction. That could be for any number of reasons such as, in the eyes of the potential contributors, ask is too big, or maybe it seems like someone is developing a commercial product and asking for volunteer help. There are even situations in which the OP is told that they should actually hire someone for the task (sometimes because of the size/complexity or commercial nature of the request, or other times just for practicality -- for example: the issue may need more specific or even on-site help).

It is, however, not permissable for a user to solicit jobs or payments on these forums. We do not allow posts to the effect of "I'm a developer for hire" or "I'll fix your issue if you pay me." If such posts appear, especially unsolicited with respect to any offers to pay for such services, they should be ignored and flagged. If they are truly unsolicited, they will be taken down, and the poster responsible for said posts may have administrative actions imposed.

Moving on...
As a general rule, a poster may offer to pay for specific help. While we don't encourage this, it's not against the rules. In that situation, if one or more contributors engage such an arrangement, all of the details (including scope of work, method and amount of payment, and all other aspects) become a private agreement strictly between those users. The agreement, deliverables, guarantees, payments, and any necessary arbitration will be the sole responsibility of the people involved in the agreement. The OpenWrt project itself will not be (and will not get) involved in any way and will not arbitrate or enforce any aspects of the agreement.

With all of that said, if it comes to the attention of the OpenWrt project that any such agreements are being formed for malicious or illegal purposes, we may take administrative action against said users such as terminating their accounts.

10 Likes

Did you clone my tree and copy

http://desipro.de/openwrt/23.05/ipq806x-nss/config.buildinfo to openwrtsources/.config

and

http://desipro.de/openwrt/23.05/ipq806x-nss/feeds.buildinfo to openwrtsources/feeds.conf

if yes, then make sure you ran:

openwrtsources/scripts/feeds update -a
openwrtsources/scripts/feeds install -a

so it downloads and adds all the packages to your build tree. Normal openwrt feeds do not contain the nss packages. Once this is done you can use:

make V=s menuconfig

to change the selection of software that you want to be directly included or removed in the build.

3 Likes

I cloned @ACwifidude tree and feeds. Do yours support the OnHub routers? I'm trying to sort a lot of new stuff (new to me). The compiling the image is a long process, but I'm learning WTF is going on here and I'll master this procedure too. If people tried it, they might not wonder why I thought of paying for someone's time to do it for me and make sure it's done right.

Yes, you just have to change the config, through:

make V=s menuconfig

Then change Subtarget to Google Chromium and afterwards change Target Devices.

I'm not sure I know exactly how to do this from the command line. What I did was enter @ACwifidude instructions:

git clone -b openwrt-23.05-nss-qsdk11 https://github.com/ACwifidude/openwrt.git

Is there a command like that I use to clone your tree and copy?

The next step in @ACwifidude process was:

./scripts/feeds update -a && ./scripts/feeds install -a && cp diffconfig .config && make defconfig && ./scripts/getver.sh

How would this step work with your scripts?

I'm at a much lower level of skill here. Don't want to waste too much of anyone's time.

git clone -b openwrt-23.05-nss-qsdk11 https://github.com/ricsc/openwrt.git
cd openwrt/
wget http://desipro.de/openwrt/23.05/ipq806x-nss/config.buildinfo  -O .config
wget http://desipro.de/openwrt/23.05/ipq806x-nss/feeds.buildinfo -O feeds.conf
./scripts/feeds update -a
./scripts/feeds install -a
make V=s menuconfig

Now change Subtarget to Google Chromium and then select Target Devices:
Screenshot_20240609_002155

After saving run:

make V=s

or if you want to build with multiple cores:

make V=s -j 6 world

1 Like

Thanks for writing this out for me and hassling with a rookie. I think this is really going to work! It's all actually making sense.

I got an error after

./scripts/feeds update -a

The error message says:

fatal: 'f3994a3' is not a commit and a branch 'f3994a3' cannot be created from it failed

And...

ERROR: please fix feeds/packages/lang/python/micropython/Makefile - see logs/feeds/packages/lang/python/micropython/dump.txt for details
ERROR: please fix feeds/packages/libs/efivar/Makefile - see logs/feeds/packages/libs/efivar/dump.txt for details

Yep sorry, the feeds.conf is wrong it should read:

src-git packages https://github.com/openwrt/packages.git;openwrt-23.05
src-git luci https://github.com/openwrt/luci.git;openwrt-23.05
src-git routing https://git.openwrt.org/feed/routing.git;openwrt-23.05
src-git telephony https://git.openwrt.org/feed/telephony.git;openwrt-23.05
#src-git nss https://github.com/ACwifidude/nss-packages.git;NSS-11.2-K5.15
src-git nss https://github.com/ricsc/nss-packages.git;NSS-11.2-K5.15

This is what my local feeds.conf looks like, it seems like in generates the feeds.buildinfo when building.releases

What do I change in the process you described originally?

git clone -b openwrt-23.05-nss-qsdk11 https://github.com/ricsc/openwrt.git
cd openwrt/
wget http://desipro.de/openwrt/23.05/ipq806x-nss/config.buildinfo  -O .config
wget http://desipro.de/openwrt/23.05/ipq806x-nss/feeds.buildinfo -O feeds.conf
./scripts/feeds update -a
./scripts/feeds install -a
make V=s menuconfig

Just do the following:

git clone -b openwrt-23.05-nss-qsdk11 https://github.com/ricsc/openwrt.git
cd openwrt/
wget http://desipro.de/openwrt/23.05/ipq806x-nss/config.buildinfo  -O .config
./scripts/feeds update -a
./scripts/feeds install -a
make V=s menuconfig
1 Like

I got an error here, ".config is not a directory"

I'm assuming this is what's intended?

wget http://desipro.de/openwrt/23.05/ipq806x-nss/config.buildinfo -O ~/openwrt/.config

Thanks