Package Details: micmac-git 1.1.1.r247.ge4b1c2384-1

Git Clone URL: (read-only, click to copy)
Package Base: micmac-git
Description: Free open-source photogrammetry software tools - Version GIT
Upstream URL:
Keywords: photogrammetry
Licenses: custom:CeCILL-B
Conflicts: micmac
Provides: micmac
Submitter: geosam
Maintainer: eclairevoyant
Last Packager: eclairevoyant
Votes: 4
Popularity: 0.000214
First Submitted: 2019-11-06 17:16 (UTC)
Last Updated: 2023-09-21 12:11 (UTC)

Dependencies (9)

Required by (0)

Sources (1)

Latest Comments

1 2 Next › Last »

berilac commented on 2024-05-25 06:47 (UTC) (edited on 2024-05-25 06:49 (UTC) by berilac)

Tried building outside of a chroot using the same instructions found in the PKGBUILD's build(). Seems to build fine, but oddly considerably faster, by what feels like an order of magnitude. The chroot'ed output is also much more verbose - prints a lot more warnings. Trying to determine what's different.

So far, I've found a difference in the FLAG variable set by cmake.

In the chroot, it is this:

-march=x86-64 -mtune=generic -O2 -pipe -fno-plt -fexceptions -Wp,-D_FORTIFY_SOURCE=3 -Wformat -Werror=format-security -fstack-clash-protection -fcf-protection -fno-omit-frame-pointer -mno-omit-leaf-frame-pointer -Wp,-D_GLIBCXX_ASSERTIONS -flto=auto -std=c++11

Outside the chroot it's only this:


Presumably the compilation speed is at least in part to do with a lack of -O2.

berilac commented on 2024-05-17 17:26 (UTC)

Ok, so it looks like it's building from code in the repo. src/uti_phgrm/GraphCut/QPBO-v1.4. I've had no luck so far determining the source of the problem.

berilac commented on 2024-05-17 13:47 (UTC) (edited on 2024-05-17 13:53 (UTC) by berilac)

Getting a bunch of linker errors; all (so far) related to QPBO, e.g.:

[ 89%] Linking CXX executable mm3d
/usr/bin/ld: /tmp/cc3M52dF.ltrans66.ltrans.o: in function `QPBO<int>::MergeParallelEdges()':
<artificial>:(.text+0x6a81): undefined reference to `QPBO<int>::MergeParallelEdges(QPBO<int>::Arc*, QPBO<int>::Arc*)'

"Full" output (from the same starting point as above) here:

I've tried looking it up, with not much clear success. Might it be a missing dependency or could something else be the matter? I'll keep digging myself as well.

eclairevoyant commented on 2023-09-21 12:11 (UTC)

@dreieck chill out, no need for the long essay. I already said the same a while back, if you read the comments, just didn't get round to updating this yet.

Anyway it's updated now.

dreieck commented on 2023-09-21 11:54 (UTC) (edited on 2023-09-21 11:54 (UTC) by dreieck)

Please remove dependency on python-argparse-shim. This is not needed at all. python-argparse is part of core python. python-argparse-shim is only there for packages which have not been fixed yet and still depend on python-argparse, to fulfill their dependency.

Depending on python-argparse-shim is pointless, superfluos, and might break when python-argparse-shim is to be deleted because it came obsolete.

Thanks for maintaining!

haawda commented on 2023-09-09 05:04 (UTC)


eclairevoyant commented on 2023-09-02 07:57 (UTC)

@MarsSeed, no, it shouldn't depend on anything related to argparse, because argparse is part of the python language already. Depending on the shim is pointless, the "shim" does absolutely nothing

MarsSeed commented on 2023-07-18 23:50 (UTC) (edited on 2023-07-18 23:51 (UTC) by MarsSeed)

Please kindly make this depend on python-argparse-shim to eliminate using the deprecated and problematic python-argparse, and letting this application use the natively built-in Python argparse functionality.

dreieck commented on 2023-05-12 12:24 (UTC)

python-argparse must be removed from the depends array, see ↗ here.

Thanks for maintaining!

soenke commented on 2021-11-09 15:08 (UTC)

Thanks to some good sugggestions in the GitHub Issues, I was finally able to build a package.