Replies: 3 comments 4 replies
-
What does it say if you do?: ls /usr/local/include/boost |
Beta Was this translation helpful? Give feedback.
-
Here's a little bit of a self-discovery update: I was snooping around the files, and especially the meson folder and saw that within the "osx.ini" and redirected the inputted root location to the supposedly proper one instead of the /opt/ one, and managed to get past the "missing" boost dependency error, however still no .app output manifested from the whole process. Here I shall provide a plain-text document (modified to remove sensitive information, of course) of what had transpired upon making that modification. From brushing through it, either I don't have enough dependencies to proceed properly or I'm getting something mixed up all together. NOTE: I am using an Intel machine, so hopefully that should narrow things down more. I did try the osx-intel.ini along side the subs.ini file Looking forward to hearing from you! |
Beta Was this translation helpful? Give feedback.
-
I sincerely apologize, however, I do not see how this is exactly helpful.
I've followed your guide as well as modified the .ini file as directed by
you, but whatever build directory the meson.build file is calling for
doesn't seem to exist.
…On Mon, Feb 26, 2024, 11:07 Michael Fisher ***@***.***> wrote:
Advice: learn meson: https://mesonbuild.com/Quick-guide.html
—
Reply to this email directly, view it on GitHub
<#759 (reply in thread)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AQESTS32UNZCKAUXXCVRE3DYVSXNNAVCNFSM6AAAAABDZFVAF6VHI2DSMVQWIX3LMV43SRDJONRXK43TNFXW4Q3PNVWWK3TUHM4DKOJUGU4TA>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
Beta Was this translation helpful? Give feedback.
-
Good afternoon. To get straight to the point, I have brew installed as well as meson (via brew) as well as the boost dependency library as mentioned in the "build.md" file provided-- tried punching in the build code (
BOOST_ROOT="/usr/local/include" meson setup...
) only to receive the following:Without a generated "Element.app" which was to be expected from an ill-prepared build process.
I assumed that I had to change the directory to "element-develop" prior to building it, or at least attempt to.
Any and all help with this would be greatly appreciated, as I do enjoy Element! Apologies in advance if this issue report doesn't fit the tolerated criteria for validation.
Beta Was this translation helpful? Give feedback.
All reactions