![]() Since as far I know, nobody here uses an apple m1 computer, and accodingly, pre-compiled binaries are not available yet.įind someone who can build those on your computer, test them and provide them to Mtex so we might be able to provide an AArch64 version We can cover those, which we have available and for which someone volunteered to compile nfft. ![]() We would like Mtex to be as easy as possible to run on many different operation systems. ![]() But it may require that the user may also use the google, since - at least from my side - I don't have the capacity to start from the big bang birth of the universe and I don't have an apple M1 to try those thigns out. Given that there are many versions of macOS around and given that we cannot cover all possible variations, I may try to update the relavant parts of the instruction such that might become clearer what people may have to change adapt. things like the PATH variable, basic terminal usage. However, in some (most?) constallations, those solutions also assume, that users at least an infinitesial understanding of how the operation system works at the userland side (e.g. ![]() Therefore, people developed package managers like homebrew, fink or macports to actually allow users to easily install things which are not available from apple and too tedious to install manually. The key problem arises form the fact, that apple does not really offer a developer friendly environment when it comes to something outside the walled garden of the app store. I agree, that once we were writing these instructions, we assumed that users would at least be familiar with the very basic terminal usage and logics and be either able to do make the relevant changes according to their specific os version or report the relevant problem in the forum (e.g. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |