10. Frequent Asked Questions

10.1. I’m planning to start a small/medium/big/huge project, is pyke a good choice?

Pyke is a good choice for any project size. On small projects it allows you to start quickly without any configuration, usually with a couple of lines.

For big and huge projects it has many features, but I would pay special attention to:

  • easy definition of rules to build really complex software
  • the syntax encourages maintainability
  • pyke is fast!

10.2. Is pyke multiplatform?

Absolutely! It runs on linux, mac and windows, and it runs fast on all platforms.

10.3. Can pyke build projects for linux/mac/windows?

Yes! Pyke should work on an distribution that supports python. Just to name a few, it should work on ubuntu, debian, red hat, fedora, ...

10.4. Can pyke build projects for iPhone?

Yes! You just need a mac with python installed.

10.5. Can pyke build projects for Android?

Yes! Use any platform supported by the Android SDK.

10.6. Is pyke the best build tool available?

Of course!! What do you expected to read on the pyke’s documentation page :p

Anyway, that’s the wrong question. A better question would be:

Is pyke the best build tool for my project?

And to be honest, each project has its own needs. I tried to make pyke multiplatform, extensible, easy of use and really fast. I don’t really have the answer, but I tried many build tools over the years and I made a tool that I love to use. Is it the best for everybody in all situations? I doubt so, there is no single tool that fits all needs for everybody...so here is my advice, try it for free and see if it feels a good fit for your project, if so, buy it and use it, if not, then try another tool.

10.7. Will pyke be hard to learn?

Although it should have a very low learning curve (even lower if you know python) it might take some time to learn, hopefully mastering it should be easier than other build tools.

10.8. Is it possible to build things in parallel?

Yes indeed! Pyke builds things in parallel unless you tell the tool otherwise. It internally gets all the details about how files should be processed, and starts many processes in parallel.

It also tries to abstract at the highest level how things are parallelized, so you only have to worry to define your rules, but not on parallelization.