References :

• yarn
• composer
• cocoapods
• ...

There is many other but they are good one

Great! I have finished the xmake repo plugin task to manage repositories.

for example:

$ xmake repo --add origin https://github.com/tboox/xmake-repo.git
$ xmake repo --add other-repo https://github.com/xxxx/other-repo.git

Or use global add_repositories api in xmake.lua:

add_repositories("origin https://github.com/tboox/xmake-repo.git")
add_repositories("other-repo https://github.com/other/other-repo.git")

And the xmake-repo is the default repository, we need not add it manually.

And we can add requires and add package dependencies (developing ..)

Add requires:

add_requires("tboox.tbox >=1.5.1", "zlib >=1.2.11")
add_requires("zlib master")
add_requires("xmake-repo@tboox.tbox >=1.5.1")
add_requires("https://github.com/tboox/tbox.git@tboox.tbox >=1.5.1")

Add package dependencies:

target("test")
    add_packages("tboox.tbox", "zlib")

If you run xmake require or xmake require --install, xmake will install and update all required packages to local project repository directory.

It's all great 👍
Actually this repo implementation is really nice and consistent. Even if I'm afraid about the future size of the xmake-repo.
A remaining task will be to automate packaging and publication on user repos.
I'm looking for semantic versioner, this is the yarn/npm one, and lua implementations.

How did you plan to handle that case?

add_requires("https://github.com/tboox/tbox.git@tboox.tbox >=1.5.1")

Excuse me, I'm wondering what's the advantage of xmake repo that git submodule doesn't have.

@uael I just place xmake.lua and other some text files (.e.g *.patch) in xmake-repo and I did not intend to place the binary file in this repository.
And you can create yourself private repository to place some packages and binary files for each archs and platforms.So it will not be too large.

• add_requires("https://github.com/tboox/tbox.git@tboox.tbox >=1.5.1")

add_requires can process it directly If this project has complete tags like 1.2.1 or v1.x.x and it will define a package named tboox.tbox. We can use add_packages("tboox.tbox") to add package denpence to target.

If this git project has not tags, we can set a branch name, for example: add_requires("https://github.com/tboox/tbox.git@tboox.tbox master")

Or you can directly define package("tboox.tbox") to describe custem rules in xmake.lua if cannot get git tags, for example:

package("tboox.tbox")
      add_versions("1.5.1", "1.6.0", "1.6.1") -- we can add a version list if no git tags
      set_url("https://github.com/tboox/tbox/archive/v$(v1).$(v2).$(v3).tar.gz")
      on_build(function ()
           -- if need
      end)
      on_package(function ()
           -- if need
      end)

add_requires("tboox.tbox >=1.5.1")

We also use package("xxx") to describe every package in xmake-repo or other private repositories.

@titansnow git submodule is great, but xmake repo and xmake require will provide more convenient cross-platform package management.

Some advantages:

• Do not need user to manage each third-party package
• Better version control
• Support .tar.gz or .zip package if the dependent package does not have a git repo, but git submodule need it.
• Automated package compilation and linking to the given target.
• Support multiple platforms, architectures and languanges.

In most cases, you only need to add two lines in xmake.lua to link dependent package automatically which exists in xmake-repo.

add_requires("pcre2 >=1.2.0", "zlib >= 1.2.11")
target("test")
    add_packages("pcre2", "zlib")

Then run:

$ xmake 

And it will show tips when the version of package dependences have been changed in xmake.lua

This project exists outdated package dependences, update them now? y (y / n)
y
installing and updating outdated package dependences ... (call `xmake require` automatically)
building project .. (`xmake build`)

@uael semver.lua is great 👍. I will consider using it.

Sounds like fun. Like it:heart:. May it be hard work?

@titansnow actually the following isn't possible with git submodule:
foo depends on bar;
foo depends on baz;
bar depends on baz;
then with package management the foo vendor dir look like:

vendor
|__ bar
   |__ ..
   :
|__ baz
   |__ ..
   :

In the case of provided binary files i just dunno how to handle it properly, wondering what's your feeling about it

I got it @uael

As for me I prefer "code once, compile everywhere" @uael

"code once, compile everywhere" does not prevent to avoid compile time on large build with a bunch of dependencies 👍

@waruqi repositories shouldn't being cloned globally ? Like on on ~/.cache/xmake/repositories/

uael@leopard:~/.cache$ tree xmake/
xmake/
└── repositories
    └── xmake-repo
        ├── libuv # vendor level
        │   ├── libuv # package level
        │   │   ├── 0_1_0.lua # contains specific version informations
        │   │   ├── 0_1_3.lua
        │   │   ├── 0_2_0.lua
        │   │   ├── 0_2_6.lua
        │   │   └── xmake.lua  # general package informations
        │   └── xmake.lua # general vendor informations
        ├── tboox
        │   ├── gbox
        │   │   ├── 1_0_1.lua
        │   │   ├── 1_0_2.lua
        │   │   ├── 1_0_3.lua
        │   │   └── xmake.lua
        │   ├── tbox
        │   │   ├── 1_5_3.lua
        │   │   ├── 1_6_0.lua
        │   │   ├── 1_6_1.lua
        │   │   └── xmake.lua
        │   └── xmake.lua
        └── zlib
            ├── xmake.lua
            └── zlib
                ├── 1_2_11.lua
                └── xmake.lua

9 directories, 18 files

With this structure we can clone the xmake-repo on xmake install and cache packages and versions until the next repository pull. When another repository is added, the cache is updated.
Then global package are downloaded in ~/.cache/xmake/packages/, and local packages in $(buildir)/packages/

Seems right

Maybe git large file storage is suitable for you @uael

@uael Yes, I'm planning to clone repositories globally in the first time and then only need to git pull to update them when the repositories need be updated. And I will continue to optimize it in future.

I added a optional mode for add_requires("zlib >=1.2.11 optional") api. If this package is optional dependent, we will do not download and install it automatically by default, unless the user runs xmake require zlib to install it.

For example (projectdir/xmake.lua):

-- define package
package("mbedtls")
    set_url("git@github.com:ARMmbed/mbedtls.git")
    on_build(function (package)
    end)
    on_install(function (package)
    end)
package_end()

-- requires
add_requires("mbedtls master optional")    -- optional dependent package
add_requires("zlib >=1.2.11", "xmake-repo@tboox.tbox >=1.5.1")
add_requires("git@github.com:glennrp/libpng.git@libpng >=1.6.28")

Love it 👍
Can be really useful for multiple and optional backend for example, is there a way to test if installed with the lua api ?

You need test installed packages? xmake will first detect whether a package has been installe, then install it if it does not exist.

More I look at your commits on repo, more I seriously envisage to use lua 👍
Forgot to answer you! No I mean add some defines, for example, to know in the code if an optional package is installed or not.

you can use is_package("xxx"), for example:

-- require package for `xmake config --zlib=y|n` or checking and installing automatically
add_requires("zlib >1.2")

target("xxxx")
    set_kind("binary")
    add_files("*.c")
    
    if is_package("zlib") then
         add_defines("-DZLIB_ENABLED")
    end

is_package will return true If the zlib package is enabled and installed.

#75

I rename xmake deps action to xmake require. for example

# install all package dependencies in xmake.lua
$ xmake [q|require]

# install the given required packages manually
$ xmake require zlib tboox.tbox
$ xmake require "zlib >=1.2.11" "tboox.tbox master"
$ xmake require "git@github.com:tboox/tbox.git@tboox.tbox >=1.6.0 <1.6.1 || master"

By the way, may I ask how soon repo would be merged back to master? Or never? @waruqi

I just updated from the latest repo

uael@aero:~/xmake/tests/projects/deps_console_c$ xmake require -v -f
error: /home/uael/xmake/tests/projects/deps_console_c/xmake.lua:2: attempt to call global 'package' (a nil value)
stack traceback:
    [/home/uael/xmake/tests/projects/deps_console_c/xmake.lua:2]: in main chunk

It's maybe badly installed from me 😸
I run make build then the get.sh with __install_only__ and __local__

@uael This should be a installation problem. It will be installed to /usr/local directory by default if we run make build; sudo make install. And it will be installed to ~/.local directory if we run scripts/get.sh __local__.

So maybe the previous version has not been uninstalled or updated and you're running the old version of xmake.

You can attempt to run sudo make uninstall to remove old version first and try installing it again.

Hi @waruqi, how is this going ? I'm currently passing some exams cannot follow as before 😢

@uael Thank you very much for your contribution and help. The semantic version module is very great now.

I'm implementing find_package to detect and link the dependent packages and I'll finish the rest of the job as soon as possible.

And I haven't had much time to focus on semver module lately. If there is a problem with the semantic version in the future, I will try to modify it and submit pr and issues to you.

Thanks!

@uael I'm so sorry I spent too much time in order to implement the detect modules, so the development of package management was delayed.

Now I'm going to continue to start this job and hope to be able to complete it in v2.2.1 version.

I have merged all patches of the repo branch to dev branch and will remove repo branch.

Because there are too many conflicts, I can only merge code manually, and I'm sorry that I didn't keep the information of contributors. 😭

A test example:

$ cd xmake/tests/project/requires
$ xmake

I am improving the dependent environment of requires on each platform (git, curl, ..).

Can I usr remote package management now?

@yangjz1125 Not yet, I am processing other issues now.
This feature is also in development, the next version can be used. Please wait some time.

Okay, thanks.

An example: https://github.com/tboox/benchbox

Run:

$ git clone https://github.com/tboox/benchbox.git
$ cd benchbox
$ xmake

@yangjz1125 @uael This feature can be used for v2.2.2

An example project: https://github.com/tboox/benchbox

Documents:

• English
• 中文

add_requires("tbox 1.6.*", "libpng ~1.16", "zlib")

target("test")
    set_kind("binary")
    add_files("src/*.c") 
    add_packages("tbox", "libpng", "zlib")

Very good work here, repo/package are a well designed approach. I really have to pick a side project to try it out!

I just finished the docs, thank you for quoting me 😃 Very accurate and understandable by the way

I have almost completed this feature, and I will continue to improve it and the package repository. xmake-repo

Documents: https://xmake.io/#/home?id=remote-dependency-mode