Small omission in the guide: it is implied in step 9 that a {} literal should be parsed as a hash-map in the reader, but this is never explicitly stated earlier on. The sentence in question is: "This is basically the functional form of the {} reader literal syntax".

What are the steps to reproduce this issue?

1. create tweak and preferences bundle (bin/nic.pl)
2. run make package install
3. go to settings

What happens?
There is no preferences for new tweak. This is because Preference Loader not installed. It should be described in wiki.

What were you expecting to happen?
There is information about Preference Loader requirement in wiki.

If yo

I haven't started work yet, but I wanted to mention that there is one more conan-related project for XMake I want to do which is called a "Build Helper".

https://docs.conan.io/en/latest/reference/build_helpers.html

The documentation for the CMake helper provides the justification here:

https://docs.conan.io/en/latest/reference/build_helpers/cmake.html

In summary, helpers make the Con

Task has some tricky gotchas that are not well documented. I need to work on improving some areas and add some missing documentation.

• Add a variable priority section better explaining how them work.
  • Make it clear that setting a var through cli (not env) kinda overrides it. (Ref).
• More itens to be added

Some tasks are self-explanatory if you looked at their script and need no description. I also think knowing what script the task actually runs can be helpful context if only reading from the help dialog and not the maidfile itself.

For instance, I have a clean task that just runs rm -rf build/. If the help dialog outputted this, I wouldn't need to add a description, but since it doesn't I

There's some very useful documentation hidden in https://github.com/mxe/mxe/wiki and I'd like to make this available in the main tree (with the longer term aim of moving all docs to wiki/markdown style and reserve index.html for "website" info - intro, contacts, external links etc).

Does anyone have experience with keeping these in sync?

Hello,

So, the link to the presentation or whatever it was in the readme is broken. That file is no longer available.
Is there any kind of tutorial that could be used to learn how to use Genie?
Can I just look for any premake4 tutorials and that would be enough?

Cheers,
Furai

Currently, if I run bake command when the Bakefile is empty, the error message seems very scary:

Traceback (most recent call last):
  File "/home/redowan/.local/share/virtualenvs/flask-template-wBuRwttx/bin/bake", line 8, in <module>
    sys.exit(entrypoint())
  File "/home/redowan/.local/share/virtualenvs/flask-template-wBuRwttx/lib/python3.7/site-packages/click/core.py", line 764,

In particular that HOMEDRIVE and HOMEPATH need to be set, and that they should be set through /etc/profile.d/* files to make sure they are set regardless of user being logged in.

The issue is that without these the Erlang distribution will try to save the cookie in C:\Windows.

--warn-undefined-variables is really useful, but some modules are relying on undefined variables being empty, and they generate the checks in thousands. Not always they can be rewritten.
In this cases, it would be beneficial to have a pragma-like comment to suppress the warning for some of lines.
grep-ing them out would only help if the code testing the variable is not in $(eval).

Upon every successful run of sbt compile an extra (and identical) copy of the file resolved.xml.xml is created inside "sbt-pack\target\sbt-1.0\resolution-cache\org.xerial.sbt\sbt-pack\scala_2.12\sbt_1.0\HEAD+{time-stamp}"

is this on purpose?

The lib needs to be cleaned up and documented so others can use it more easily.

While reading the guide, I see that the code snippets are missing for some reason, such as this:

Is there a way to get them, I would love to follow up with the guide.

Thanks a lot for your effort.

Would help to test if checkmake still works (after refactoring) and also to illustrate how each rule works.

our prior recommendation, removed in 4bb8d76177c40c9a0405ca66da9a40dcbded4505, caused issues with makefiles on ubuntu 16.x (xenial), i.e., on our staging server, such that all recipes failed with the error "No such file or directory". do some research on directives, identify the culprit, and add a new, portable set of default directives.