bkoropoff/makekit

MakeKit build system

makekit's Issues

0.1 release tag missing

There used to be a 0.1 release tarball when hosted on sourceforge. It would be nice to have a v0.1 tag at the point where 0.1 was done. (and maybe tag a 0.2 release?)

Releases are helpful for us who packages stuff for distros.

Thanks

`makekit init` cannot find makekit script for copying

It looks for it in $MK_HOME, but that's not the same as where Makekit resides.

On my system, Makekit lives at /usr/local/bin/makekit. I've tried deciphering makekit puts itself in there, but I can't make heads or tails of exactly where it does so. Can you give me a quick point in the right direction?

Allow INCLUDEDIRS to accept absolute paths

The docs claim (and my own testing has verified) that INCLUDEDIRS accepts only relative paths.

It'd be neat if you could define variables with mk_declare that listed a set of related header files, and then use those variables in INCLUDEDIRS parameters in other MakeKitBuild scripts, thereby reducing the amount of redundant listing of header directories in projects where each directory contains a MakeKitBuild file. What currently prevents this is that INCLUDEDIRS must take relative paths (which wouldn't resolve consistently across several MakeKitBuild files). If INCLUDEDIRS were able to accept absolute paths, you could use mk_resolve_target and mk_declare to build a list of include directories, and reuse it everywhere.

Add missing documentation to low-level API functions

Automate creating release tarballs

Document extending MakeKit

The documentation should cover, at a minimum:

• How to write custom build targets
• How to write helper functions to generate custom targets
• How to create custom modules

Nice-to-haves:

• MkDoc syntax reference

Document support for recursive groups

Currently mk_group doesn't accept the GROUPS parameter, which means you're limited to a depth of one when creating group hierarchies. It'd be awesome if you could build arbitrarily deep group dependency graphs.

Add test suite

Need a way to test for regressions

Error when linking with a static library

Hi Brian,

I am trying to link with a static libaray in makekitbuild environment and I get the following error:

relocation R_X86_64_32 can not be used when making a shared object; recompile with -fPIC

Recompiling the static library with -fPIC is out of question. How to fix this problem.

Thanks
R.K

How to generate *dsc *.debian.tar.xz *.orig.tar.gz files via MakeKit

Hi, Brian
I need to submit *dsc *.debian.tar.xz *.orig.tar.gz files to our project, please tell me how to generate these files?

System 390

I noticed that makekit/mk/module/platform.sh does not support Linux running on a system 390 platform (i.e. zLinux):

uname

Linux

uname -m

s390x
This is a 64-bit Linux operating system.

When running configure I am getting:
[platform] ERROR: unknown architecture: s390x

Thanks,
Ken

rpath-link does not belong in RPATHFLAGS

This is really an implementation detail of the staging directory. RPATHFLAGS should be exclusively to control the rpath of the resulting binaries.

.configure fails with strange error

I tried cloning makekit and when I tried to run ./configure, it fails with
ERROR: please run configure from a seperate directory

What am I doing wrong?

How to create uer defined modules?

When I was going through the user manual of MakeKit on its website, I found in the MakeKitBuild file, we must first use the MODULES to include the all the modules that would be used in our project.
My question is:

1. Is there a list describing all the built-in modules that we could use and how it is used;
2. How could we define a user defined module and make it work.
   If anyone konws the answer, please!
   Thanks a lot!