The app seems to do nothing about archetype

[pavlepiramida]

I can confirm the same issue

[kjlaw89]

@aggalex Interesting... I'm actually just using GLib.File to change the folder's path. I may try to do a mv command to see if that works better.

Can you try to move the folder manually from /tmp and see if it lets you or gives you an error? In your log it was /tmp/com.github.aggalex.myapp.

[pavlepiramida]

@kjlaw89

Made work directory in /tmp,and Archetype worked as expected.
Project is created and moved,but its tied to /tmp.

[kjlaw89]

@pavlepiramida

When you say that it's tied to /tmp, what message or error are you getting when you try to move it elsewhere? As long as you remove the build directory and rebuild (which may not be necessary) it should rebuild fine. That said, I know for the Gnome Builder file that I specify the export path there and you might have to adjust that file if you move it. I'm not 100% certain on how that file works I just know it has a project path specified so I figured I'd replace it in case it was needed...

Edit: I'm also working on an update that attempts to use the mv command instead of Glib to change the directory as well. Hopefully I'll have that finished tonight and out by tomorrow. Not 100% sure on if that'll help in your case though.

[pavlepiramida]

I suck at explaining stuff 😄
Creating work directory in /tmp and setting project path to it,allows Archetype to do its magic.
It creates project specified by me,without any errors.
Moving work directory out of /tmp to any other location does not break anything at all.
I moved it to home and it built and ran without any issues what so ever.

By tied to /tmp I meant to say,that project will only be created if dest_dir is located in /tmp.

Later moving whole work directory from /tmp does not break a single damn thing.

Kudos and thanks for this beautiful app!

[aggalex]

Sorry for not replying on time, I didn't have the time too...
So I tried making Archetype generate an instance, and copying the folder created to my designated place. Archetype seems to be deleting the folder from tmp a while after, so I had to be fast. But I finally made it! Had problems with compiling it though. Ether I don't know how, or there's something missing. Here's the directory tree of my dummy app's folder:

.
├── app
├── AUTHORS.md
├── com.generic.rdnn.json
├── data
│   ├── com.generic.rdnn.appdata.xml
│   ├── com.generic.rdnn.desktop
│   ├── com.generic.rdnn.gresource.xml
│   ├── com.generic.rdnn.gschema.xml
│   ├── css
│   │   └── style.css
│   ├── images
│   │   ├── com.generic.rdnn.png
│   │   ├── com.generic.rdnn.svg
│   │   ├── icons
│   │   │   ├── 128
│   │   │   │   └── com.generic.rdnn.svg
│   │   │   ├── 16
│   │   │   │   └── com.generic.rdnn.svg
│   │   │   ├── 24
│   │   │   │   └── com.generic.rdnn.svg
│   │   │   ├── 32
│   │   │   │   └── com.generic.rdnn.svg
│   │   │   ├── 48
│   │   │   │   └── com.generic.rdnn.svg
│   │   │   └── 64
│   │   │       └── com.generic.rdnn.svg
│   │   └── screenshot.png
│   └── meson.build
├── debian
│   ├── changelog
│   ├── compat
│   ├── control
│   ├── copyright
│   ├── rules
│   └── source
│       └── formart
├── LICENSE.md
├── meson
│   └── post_install.py
├── meson.build
├── po
│   ├── com.generic.rdnn.pot
│   ├── LINGUAS
│   ├── meson.build
│   └── POTFILES
├── README.md
├── src
│   ├── Application.vala
│   ├── configs
│   │   ├── Constants.vala
│   │   └── Settings.vala
│   ├── controllers
│   │   └── AppController.vala
│   ├── Main.vala
│   ├── meson.build
│   ├── views
│   │   └── AppView.vala
│   ├── widgets
│   │   └── HeaderBar.vala
│   └── Window.vala
└── tests
    ├── assert.vala
    ├── meson.build
    └── test.vala

[kjlaw89]

@pavlepiramida So it sounds like it has some issue with moving to a directory outside of /tmp, but once it's created you can take it anywhere and it will work fine.

@aggalex I realized that when I started to look at the code last night. If it succeeds or fails it will attempt to clean up the /tmp directory of any folders created. I'll adjust that in my (attempted) fix. As for building the app, you should be able to open the terminal to your app's folder and run:

./app install-deps && ./app install && ./app test-run

install-deps will install any missing dependencies, while install will install the resources and test-run will build, test and run the application.

After you have run install-deps and install, you can just run test-run going forward. If you add any additional resources or change icons you'll need to re-run install but until then test-run is enough.

[kjlaw89]

@pavlepiramida, @aggalex Version 1.0.2 is out now. See if that helps!

[aggalex]

I will do that when I finish my economics exams. Thanks!

[pavlepiramida]

Works like a charm now!

[aggalex]

It indeed works perfectly now. Perhaps You'd like to close the issue.

[kjlaw89]

Great! Closing this out as resolved!