>yes, I use pd-lib-builder, but doesn't it automatically find the m_pd.h and pd.exe files automatically?

The Pd installer is fine for a normal user. Not for a w32 dev/tester.

I recommend that you use the zip version. You don`t want “C:\Program Files (x86)” as it has spaces in the name.

Automatically find what?

Your pd-extended installation?

Your 0.46.7 instt?

Your 0.47.1 install?

Your coming 0.48.0 install?

Your Purr-Data install?

They all have “m_pd.h” and “pd.dll”.

I also recommend:

https://notepad-plus-plus.org/

for displaying .txt that are unix/osx format. Change it at the botton right before utf-8/ansi.

Also very useful tool for programing.

Salutti,

Lucarda.

Mensaje telepatico asistido por maquinas.

From: Pd-list <pd-list-bounces@lists.iem.at> on behalf of Alexandre Torres Porres <porres@gmail.com>
Sent: Tuesday, January 24, 2017 11:47 PM
To: Christof Ressi
Cc: pd-list@lists.iem.at
Subject: Re: [PD] building externals on windows

2017-01-24 16:23 GMT-02:00 Christof Ressi <christof.ressi@gmx.at>:

If you use pd-lib-builder, just open the shell, 'cd' to the directory of the makefile and type:

make pdincludepath={path to m_pd.h} pdbinpath={path to pd.exe}

make install objectsdir={where you want to install}

yes, I use pd-lib-builder, but doesn't it automatically find the m_pd.h and pd.exe files automatically?

cheers