Development environment guide does not explain how to build micromamba

[corneliusroemer]

I'm trying to contribute and am following the "development environment" guide: https://mamba.readthedocs.io/en/latest/developer_zone/dev_environment.html

I noticed the guide says nothing about how to build micromamba from source. None of the Cmake presets build micromamba.

[AntoinePrv]

Hi @corneliusroemer, thanks for the feedback.
mamba and micromamba are the same executable, only micromamba is a statically linked version of mamba, so it's only a matter of playing with BUILD_STATIC... options in CMake.

I do not recommend building statically for development. I'd say there is no added benefits.
If you want to make an install from source, check out the install doc, or the feedstock.

[corneliusroemer]

Thanks for your quick response @AntoinePrv

mamba and micromamba are the same executable, only micromamba is a statically linked version of mamba

I thought micromamba implemented a subset of mamba, so it's not quite the same? Or has this changed?

https://mamba.readthedocs.io/en/latest/user_guide/micromamba.html

I do not recommend building statically for development. I'd say there is no added benefits.

In that case one can't run the micromamba integration tests? Or how do you do that with mamba instead of micromamba?

Talking about this:

https://mamba.readthedocs.io/en/latest/developer_zone/dev_environment.html

so it's only a matter of playing with BUILD_STATIC... options in CMake.

My suggestion was exactly to document this so that potential contributors have an easier time getting started. The "only" can mean minutes to hours for everyone from scratch unless it's documented/shared.

May I suggest you close this issue as "no planned" as opposed too "completed" (this is a somewhat recent Github issues feature, things turn up grey then to distinguish issues based on outcome).

[corneliusroemer]

Specifically, how would I debug the failing tests here without building micromamba?

#3921

Can I just use build/micromamba/mamba instead of micromamba? That'd be great!

In that case, the development guide could suggest that instead of micromamba :)

[AntoinePrv]

I thought micromamba implemented a subset of mamba, so it's not quite the same? Or has this changed?

That is a relic from mamba 1.0, gonna fix it.

In that case one can't run the micromamba integration tests? Or how do you do that with mamba instead of micromamba?

So being the same executable, and because dynamic linking is preferred to develop, you'd run with mamba.

export TEST_MAMBA_EXE="${PWD}/build/micromamba/micromamba"

Gonna fix it too, and we should considered also renaming the folders.

Can I just use build/micromamba/mamba instead of micromamba? That'd be great!

Yes exactly!

Ans since the tests are very longs, you can also filter down with Pytest options python -m micromamba/tests/ -k <test_name>.

My suggestion was exactly to document this so that potential contributors have an easier time getting started. The "only" can mean minutes to hours for everyone from scratch unless it's documented/shared.

I agree with you, I think we still have a lot to do to make it easier to onboard !

May I suggest you close this issue as "no planned" as opposed too "completed" (this is a somewhat recent Github issues feature, things turn up grey then to distinguish issues based on outcome).

Sure