Some tips:
- Unless the code is very small, or your feature is very big, try to put blinders on, and focus only on the code you absolutely need to to get your feature built. Use search tools to comb through the code to find the relevant methods while reading as little surrounding code as possible, tweak those methods to be different, and call that a first draft. If the maintainer wants the code refactored or differently arranged, they can help with that as part of the review process
- Being unable to build sucks, it really does. But if the software is released for your platform, it means someone out there is able to build it. And these days that someone is often an automated build tool that runs per release. See if you can figure out how this tool works. What build steps it uses, what environment it runs in, etc. If you can't figure that out, try contacting the person who releases the builds
- If the software is in apt (if you're on a Debian-based system), you can use
apt build-dep
,apt source
, anddebuild
to try and recreate the native apt build process. These tools will give you the source that built the system package, and its dependencies, and allow you to build a deb yourself out of it. Test the build to make sure it's working as-is. If it is, and if the software's dependencies haven't changed too much, you can even use apt to fetch the old version that's in the repos, update the code to reflect the upstream release, and then test the build there to see if it still builds. If so, now you have something you can start working off. - If you aren't on an apt system, but do have a package manager, I assume there's an equivalent to the workflow mentioned above
- If your change is subtle enough that you think it's pretty low-risk, you could just edit the code even though you can't build it. This might be sufficient for bug-fixes where you just need to check something is greater than zero, or features where you pass a true instead of a false in certain conditions or something. You should probably mention this in your PR / MR / Patch so the reviewer knows to test building it before merging.
- This one is a bit wild, but let's say you're on a Mac or Windows machine, and the build instructions only work for Linux. You can just run a virtual machine that's got Ubuntu or something running on it, and use it as your build environment. These days you can probably be in a simpler situation with Docker or something more lightweight, but as a worst-case scenario, a full virtual machine is there for you if you need it
- And finally, if the tool isn't a crazy popular or busy tool, it's possible the maintainer or other people in the community are more approachable than you think. If they are looking for contributions, then getting a willing contributor's build environment setup is a benefit to the project. Improving their build docs helps not just you, but potential future contributors as well. A project will usually be more helpful towards someone who says "I'm trying to build this feature, but I'm running into trouble" compared to someone saying "why doesn't your tool do X". You may need to be a bit patient, they're probably doing this on volunteer hours, but they might be happy to help you get your stuff sorted out
Good luck out there, and try not to be discouraged!