>Try this:
[zexy/z~]

[externdir(
|
[classinfo z~]
|
[print externdir]


What does it print out?

> Right, this gives the “/purr-data/packages/win32_inno/build/extra/zexy”

Ok, that's good news.

>What are the arguments to those [declare] objects? 

> [declare -path data/externals/bin] --> this is relative to the patch and works on Vanilla for all OS cuz there I put what is needed for that.

Ah, I see.  GUI externals need to be ported.  There's a ported version of
ggee/image in Purr Data.

>Are you talking about the build environment you just created, or the installer? 

> Build-env & installer = 2.68 GB

Right, that's everything in C:\msys64

> installer = “C:\msys64\home\Lucarda\purr-data” = 1.07 GB

If you're measuring after building, that is:
full git repository for Purr Data
all git submodules
all binaries compiled in place
all binaries copied to build/
nw.js binary
nw.js binary copied to build/
(if you installed inno setup, all build/ copied to the installer file)

-Jonathan



Mensaje telepatico asistido por maquinas.



From: Jonathan Wilkes <jancsika@yahoo.com>
Sent: Friday, January 13, 2017 3:56 AM
To: Lucas Cordiviola; Alexandre Torres Porres; pd-list@lists.iem.at
Subject: Re: [PD] Purr Data rc4
 
> Cool,



> FYI I could successfully build, attached screenshot, but i`m gonna unninstall msys2 and delete purr-data(1) cuz both things are about 2.5GB and normally I use small C:\ drives for fast recovery if the system becomes unstable/non-operational.

That's mostly the msys2 build environment and dependencies
.
The build directory is all that's needed to run Purr Data.  If you go in
C:\msys\home\purr-data\ you can move the build directory somewhere else
before you uninstall.

> Also the registry thing is necessary for externals to load so I think the thing is not really “unzip and run”. Though I could load zexy/z~, but I'm not sure which was, I mean I have different zexys installed on my system.

Try this:
[zexy/z~]

[externdir(
|
[classinfo z~]
|
[print externdir]

What does it print out?

> Also some abs that have specific [declares] were unable to open, literally no window and no errors printed on the console. I suspect those [declares] were pointing to an ggee/image that is not compatible with RC4.

What are the arguments to those [declare] objects?

> Probably the next thing will be to use the installer, but I have other priorities.

> Let me know if you wanna test something.

> BTW, excellent work!!!

> (1) I keep a copy for some time on another HD but is way big, cuz all the .o?

Are you talking about the build environment you just created, or the installer?

-Jonathan

Salutti,
Lucarda


Mensaje telepatico asistido por maquinas.