By working on Pd's manual, I can see the current priority is to look first in the directory containing the patch, then in the search paths. I still want to maintain that structure. I just think that the order of the paths should be different, first with "standard paths" (which includes 'extra') then the user added paths.
I think you are right that the core "extra" externals should have priority. We've clearly de-emphasized users during everything into "extra" so, at this point, there shouldn't be much to break for people's setups.
That's my macOS perspective. I suppose the situation might be a little different for some Linux packages?
-------- Dan Wilcox @danomatika http://twitter.com/danomatika danomatika.com http://danomatika.com/ robotcowboy.com http://robotcowboy.com/
Hi Miller,
I've detected that your "0.50-0 test1" for win64 is built with an 64-bit wish86.exe. This one does not ship, nor load the current pdfonloader.dll that it's for 32-bit only.
I see 2 solutions:
- Build and use wish86.exe for 32bit.
- Build an 64bit "pdfontloader64.dll" and include some lines in pd-gui.tcl to auto-detect the current wish* architecture and then load the correct pdfontloader.
Mensaje telepatico asistido por maquinas.
Better yet (I think) - just include a 64 bit DLL with the 64-bit Pd and a 32-bit one otherwise.
If anyone wants to volunteer to compile a 64-bit one I'll gladly include it in teh 64-bit release (otherwise I'll try my own hand at it later this week).
I'm hoping to get the final version out Saturday :)
M
On Mon, Aug 12, 2019 at 02:37:22PM +0000, Lucas Cordiviola wrote:
Hi Miller,
I've detected that your "0.50-0 test1" for win64 is built with an 64-bit wish86.exe. This one does not ship, nor load the current pdfonloader.dll that it's for 32-bit only.
I see 2 solutions:
Build and use wish86.exe for 32bit.
Build an 64bit "pdfontloader64.dll" and include some lines in
pd-gui.tcl to auto-detect the current wish* architecture and then load the correct pdfontloader.
Mensaje telepatico asistido por maquinas.
If anyone wants to volunteer to compile a 64-bit one
Attached 64bit pdfontloader.
:)
Mensaje telepatico asistido por maquinas.
On 8/12/2019 2:31 PM, Miller Puckette wrote:
Better yet (I think) - just include a 64 bit DLL with the 64-bit Pd and a 32-bit one otherwise.
If anyone wants to volunteer to compile a 64-bit one I'll gladly include it in teh 64-bit release (otherwise I'll try my own hand at it later this week).
I'm hoping to get the final version out Saturday :)
M
On Sat, 2019-08-10 at 14:17 +0200, Dan Wilcox wrote:
By working on Pd's manual, I can see the current priority is to look first in the directory containing the patch, then in the search paths. I still want to maintain that structure. I just think that the order of the paths should be different, first with "standard paths" (which includes 'extra') then the user added paths.
I think you are right that the core "extra" externals should have priority.
I was trained by operating systems and programming languages that order is usually from local to global. I don't quite see why <pd-root>/extra should have priority. Is it considered more local than what I have in my home folder or part of my project?
Roman