Panic while copying assets about vab

[xandro0777]

it was like this, could zip it up of course if that is needed. However I get far enough to reproduce it only after working around #118.

$ git clone --depth=1 https://github.com/vlang/ui.gi
$ cd ui/examples
$ vab rectangles.v

[xandro0777]

Thanks, so far both of my issues fixed and I can work with mainline.

[xandro0777]

Moved the example to a separate directory without the "assets" subdir, the package was built but with an empty assets subdir. Scratching my head.

[xandro0777]

So apparently opt.input was "." and hence it tried to copy ./assets twice to the same place. os.cp_all returns an error saying directory not empty.

This special case can be fixed by testing opt.input is "." and avoiding to attempt co copy "./assets" twice.

But I wonder if it is required that only one "source assets" dir exists, or if it was intended that assets from several provided sources are merged that way? Or yet another alternative, stop searching further asset dirs after finding the first one?

[Larpon]

@xandro0777 - yes this looks like it might be a combination of a few issues.
You can maybe try running vab from it's project root and pass in the asset path(s) like:

cd /home/rz/prog/vab
./vab -v 3 --assets /home/rz/.vmodules/ui/examples/assets  /home/rz/.vmodules/ui/examples/rectangles.v

vab is currently dependant on having it's android directory available beside the executable if I remember correctly. So it's not too happy about it if you run it from somewhere else. In the future it will probably work like v itself by using a symlink to /usr/local/bin - or maybe we can distribute it's dependencies embedded in the executable.

[xandro0777]

So far I have no other problems running it symlinked as /usr/local/vab from a separate directory - only this issue. For now I botched around it just removing the panic call.

[Larpon]

Can you provide a minimal project / zip that I can use to test this specific scenario? Thanks in advance