please console me about usb c too
-
-
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
Joy. What is your top 5 list of downmarked skills?
-
i can cross-compile anything anywhere to any target platform.
-
Show me captures or it didn't happen x
-
https://github.com/ocaml-cross/opam-cross-windows … https://github.com/ocaml-cross/opam-cross-android … https://github.com/ocaml-cross/opam-cross-ios … all work on linux and macos and i think someone even used them on freebsd?
-
Maybe they do! Did you test?
-
freebsd isn't a supported platform because i provide support for ocaml-cross on basis of consulting and no one has paid me to test on freebsd
-
Could another member of the community not have run the tests?

-
there's no real community because most people are too sane to try things like "cross-compiling ocaml projects with substantial parts written in c to ios"
- 2 more replies
New conversation -
-
-
ah, i see, just like how i became LLVM's foremost expert on the DAG combiner.
-
the first step on that path was porting llvm's ocaml binding buildsystem from autotools to cmake. as far as i can tell no one has ever built ocaml code using cmake before, and i really hope no one will ever have to do this again
-
i've never wrote a line of cmake before that day too
-
I was dreading cmake until I worked on some scripts. MUCH easier than autodrools I must say.
-
look comparing to autotools is cheating, even bash scripts are more comprehensible
-
bash? Is that something you do to a computer after it reports a bug? Surely you mean /bin/sh, /usr/bin/sed and /usr/bin/awk and friends!
End of conversation
New conversation -
-
-
oh, does that mean I have to ask a CMake question now? Good thing I've just had issues with CMake! :D
-
aaaaaaaah (yes)
End of conversation
New conversation -
-
-
recently at work I had to debug a qmake build problem around whitespace on windows and found a feature so obscure there were a total of zero google hits for it yet it solved my problem exactly - and it was fun, is this bad
-
basically, qmake has four documentation levels: documented, undocumented (https://wiki.qt.io/Undocumented_QMake …), very undocumented (you may find odd codebases on the net using this feature), and "you have to execute the build system in your head to come up with this"
-
aw yeah qmake. brings back memories
-
have you ever used QMAKE_FUNC_*? because you may like this https://github.com/qt/qtbase/blob/5.11/mkspecs/features/file_copies.prf …
-
I didn't have to steep that low myself, I ended up using a single somewhat elegant QMAKE_FUNC_FILE_IN_<function_name> construction where if I mentioned it now, this tweet would be the only google hit
End of conversation
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.