It feels like a big leaky boat. Question 1

[gary]

Good netiquette requires asking 1 question at a time.

You have encouraged him to make a bunch of threads which look like they have same name. It’s very confusing and looks like spam. 

I posted that because he had _already_ posted 7 questions in a row.  You would know that if you had read his apology after I pointed out it was not good etiquette.

While on the subject of etiquette, it is also good etiquette to read the posts, it prevents posting incorrect comments such as yours.  Contrary to what you stated, I _discouraged_ him from asking multiple related questions in a row in separate threads.

I apologize for the trouble I've caused everyone, so please let's get back to the question itself.

[440bx]

I apologize for the trouble I've caused everyone, so please let's get back to the question itself.

You already apologized and, for most people, including myself one heartfelt apology is sufficient.

Joanna, oth, seems to have a well developed talent to create a problem where there isn't one. 

Anyway, hopefully this will be the end of that in this thread.

[gary]

I found that the GetPrebuiltDirectory UpdateBuildModes InitProject method in the lamw project fixes the paths in it, and when I write the lamw project, the paths are wrong, which leads to a series of problems.

Because the path I fill in doesn't match the fixed address, and the fixed address doesn't have a file in it!

I'm trying to understand the developer's thinking, I don't know why he did this, if you are worried about the version is not controllable, you can make a hint in a conspicuous place.

BTW, I'm a newbie, I may be wrong, I'm happy for people to correct me!

[c4p]

Hi Gary, I would try and keep to the recommended build spec for LAMW, I would recommend for anyone coming to LAMW for the first time to install it using LAMW Manager first, then do some coding on Android, and once you're familiar with the setup, then go and rebuild it with your own spec/versions, bearing in mind that some versions may not work correctly outside of the recommended spec and may cause your output to fail without more work being required (see recommended specs in the LAMW link below).

LAMW: https://github.com/jmpessoa/lazandroidmodulewizard

LAMWManager for Windows: https://github.com/dosza/LAMWManager-win
LAMWManager for Linux: https://github.com/dosza/LAMWManager-linux

I'm not saying what you've posted is wrong, as there could very well be a bug, I would just try to build LAMW using the recommended build spec first, then come back if the issue can be replicated with the recommended spec, I'm not sure what you're trying to do without the IDE, as it's tricky to generate an Android app without the IDE/GUI unless you're only doing a command line/terminal based app.

Jmpessoa has done some amazing work with LAMW but has not had much time recently to devote to LAMW due to work pressures, and if someone can flag/report any issues and fix them, they're welcome to post the corrected code on this forum, so your input with any issues are welcome.

[Joanna from IRC]

Good netiquette requires asking 1 question at a time.

You have encouraged him to make a bunch of threads which look like they have same name. It’s very confusing and looks like spam. 

I posted that because he had _already_ posted 7 questions in a row.  You would know that if you had read his apology after I pointed out it was not good etiquette.

While on the subject of etiquette, it is also good etiquette to read the posts, it prevents posting incorrect comments such as yours.  Contrary to what you stated, I _discouraged_ him from asking multiple related questions in a row in separate threads.

Ah but you were correcting him here and not on the other threads. As I said confusing 

[gary]

Hi Gary, I would try and keep to the recommended build spec for LAMW, I would recommend for anyone coming to LAMW for the first time to install it using LAMW Manager first, then do some coding on Android, and once you're familiar with the setup, then go and rebuild it with your own spec/versions, bearing in mind that some versions may not work correctly outside of the recommended spec and may cause your output to fail without more work being required (see recommended specs in the LAMW link below).

LAMW: https://github.com/jmpessoa/lazandroidmodulewizard

LAMWManager for Windows: https://github.com/dosza/LAMWManager-win
LAMWManager for Linux: https://github.com/dosza/LAMWManager-linux

I'm not saying what you've posted is wrong, as there could very well be a bug, I would just try to build LAMW using the recommended build spec first, then come back if the issue can be replicated with the recommended spec, I'm not sure what you're trying to do without the IDE, as it's tricky to generate an Android app without the IDE/GUI unless you're only doing a command line/terminal based app.

Jmpessoa has done some amazing work with LAMW but has not had much time recently to devote to LAMW due to work pressures, and if someone can flag/report any issues and fix them, they're welcome to post the corrected code on this forum, so your input with any issues are welcome.

First of all, thank you! And then thanks again to Jmpessoa for all the work. But I'm almost sure it's a version issue, I'm using a higher version of the SDK NDK other than Jmpessoa's recommendation, and the lamw code is not very friendly to newer versions, even the directory is not correct, so there's a series of should be.

So far compiling with the recommended way and version has not been a problem, but signing has been a problem again.Build Release Signed Apk prompt Unable to open file “D:\android-applAppLAMWProject5\gradle-local.... Actually the signing key was not generated, I solved it manually.

It seems that the set Path path of the gradle-local-apksigner.bat file is not correct. I don't think this is reliable either