Brilliant, thanks a lot Shawn! Karl
> On 11 Apr 2024, at 11:54 am, Shawn Laffan <shawnlaf...@gmail.com> wrote: > > Seems to work on an ARM M1 mac. > > There are no warnings raised when I install it. > > Calling /Applications/PDL/go_pdl starts a pdl shell in which I can create > ndarrays and manipulate them. > > Running pdl [home].app generates the warnings noted in the readme. Re-saving > the file as suggested works around them, after which I need to allow it to > access the relevant directories. > > > Regards, > Shawn. > > > > On Thu, 11 Apr 2024 at 09:59, Karl Glazebrook via pdl-devel > <pdl-devel@lists.sourceforge.net <mailto:pdl-devel@lists.sourceforge.net>> > wrote: > Sorry Ed, I should have said this was ARM and I needed someone with that to > test this. I will do Intel as well (+more recent versions) but right now I > just want to know if the signing works. > > Also ignore the ‘pdl [here]’ AppleScript apps, these have always been > problematic and I might need to delete them. Thanks for the feedback > > So ARM person - please try this and run the setup and try ‘pdl’ from the > command line and make sure it runs and there are no warnings > > Thanks in anticipation! > > Karl > > p.s.I looked at it but I am not sure I understand your GitHub comment? I > can’t see any version number/tag mismatches. I see there is an old ‘draft > release’ of 'SciPDL v2.025’ which I forgot to publish, I have just fixed > that and changes the name on another to make it clear which one is SciPDL. > Hope I have not made things worse…. > >> On 11 Apr 2024, at 12:30 am, Ed . <ej...@hotmail.com >> <mailto:ej...@hotmail.com>> wrote: >> >> Hi Karl, >> >> I’ve done this. I opened the “pdl [here]” from the Finder and got a warning >> that it was downloaded off the Internet. On running it anyway, I got ‘Not >> authorised to send to Finder’ described in the README. I did “Edit”, and on >> trying to save it, i+t says it’s locked. On “save anyway”, it says I don’t >> have permission to save the file and I should change permissions on it with >> “Get info”. I did it and it didn’t show as locked. I gave up on that. >> >> I tried the “source” option (I use bash) in the README, and on running “pdl” >> I got “Bad CPU type in executable” (I’m on an Intel Mac). >> >> Notes about the README: you’ve bundled 2.084, which is about a year ago. >> Also there is PDL::FFTW3 0.18 from 2021 (there’s a 0.19), PGPLOT 2.28 >> (there’s a 2.29). >> > >> Also, if we get further and you want to put it on a GitHub release, can you >> make sure it’s on an accurate tag? There was a “v2.025” added to (I think) >> 2.085. I didn’t know what it was. Please only use tags that exist on there >> already, and let me add any tags needed (there won’t be any new ones needed). >> >> Best regards, >> Ed >> >> From: Karl Glazebrook via pdl-devel <pdl-devel@lists.sourceforge.net >> <mailto:pdl-devel@lists.sourceforge.net>> >> Sent: Wednesday, April 10, 2024 10:44:02 AM >> To: pdl-devel@lists.sourceforge.net <mailto:pdl-devel@lists.sourceforge.net> >> <pdl-devel@lists.sourceforge.net <mailto:pdl-devel@lists.sourceforge.net>> >> Subject: [Pdl-devel] Mac test please? >> >> Hi there, >> >> Can a Mac user test this version of SciPDL? I’d very much appreciate it. >> (Monterey or later) >> >> https://www.dropbox.com/scl/fi/moao3dr43wxa7o1cs6cam/SciPDL-v2.084-Test.dmg?rlkey=1xcfi258mb3r88m2h0gq2x43f&dl=0 >> >> <https://www.dropbox.com/scl/fi/moao3dr43wxa7o1cs6cam/SciPDL-v2.084-Test.dmg?rlkey=1xcfi258mb3r88m2h0gq2x43f&dl=0> >> >> I am experimenting with ‘signing’ all the code using my Apple Developer ID >> and then ‘notarising' it. (Yes these are two different things** and it was >> complicated to figure all this stuff out). >> >> This all means you should not get the MacOS Gatekeeper warning about ‘code >> from an unauthorised developer’ when you run it, and it will actually run >> rather than block. (The old way was to run a nasty shell script to >> workaround this.) >> >> So should be a matter of open the DMG, drag PDL to /Applications, run the >> setup and try ‘pdl’. I need someone who is not me to confirm that it ‘just >> works’ and there are no scary warnings. Use any of the demos or your own >> code. >> >> best >> >> Karl >> >> (**TMI: Signing means it is verified as coming from me, notarising means it >> has had a malware scan on Apple’s servers, quite complex outside Xcode >> ecosystem. I had to pay $$ for a Apple Dev account). > > _______________________________________________ > pdl-devel mailing list > pdl-devel@lists.sourceforge.net <mailto:pdl-devel@lists.sourceforge.net> > https://lists.sourceforge.net/lists/listinfo/pdl-devel > <https://lists.sourceforge.net/lists/listinfo/pdl-devel>
_______________________________________________ pdl-devel mailing list pdl-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/pdl-devel
