I seem to be having trouble with yeoman scaffold installer.
I can cd to fresh directories which would be for the project files but for some reason using the yo starter it always installs build directories to desktop.
was working before, not sure what happened
You probably have a .yo-rc.json file in a parent directory.
Delete this file and it'll scaffold into your current directory.
Yeoman is warning you when this is happening, so if you read what the tool is telling you, you'll see why your issue is happening.
Related
I cannot seem to find a real solution for my problem anywhere.. After following the Capacitor documentation and creating successfully an app as well as a plugin, i've linked them both using the following commands:
in plugin directory:
-npm run build
-npm link
in app's directory:
-npm link plugin-name
-npm install
-npx cap sync
I open the app's workspace and want to run it on my device but instead I am getting an error in the added plugin of the app, that a certain library I'm using in it does not exist.
p.s
Plugin builds normally and has no issues. This occurs only after I'm linking both plugin and app. Am I doing something wrong?
The error I'm getting inside the plugin's file.
Those are the frameworks linked to the capacitor app.
As of this moment I have solved the issue I had. Shamefully there aren't really any precise documentation regarding the subject so I'll try to answer as best I can:
My issue got resolved when I updated the dependencies inside the .podspec file inside my plugin's folder.
The specific package I wish to use with the plugin, should be specified inside the .podspec file i.e. :
s.dependency 'PicUPSDKv3' should be added.
After running -npx cap sync on my main project's folder, all pods were initialized correctly and I was able to build and run the project alongside the plugin without any errors.
Running npm install unlinks whatever is linked.
You should change the order, first npm install and then npm link plugin-name.
But it's better if instead of linking the plugin you install it from its local folder.
I am trying to compile a .tex document into a pdf in TexStudio (and I have also tried in MikTex) and the following error is outputted File l3backend-pdfmode.def not found. I have tried downloading 13backend package but no luck. Do I need to place the package in a specific folder?
I had the same problem, turned out my miktex library was out-of-date
I opened "miktex console" and updated it.
I incurred into the same issue slightly after an upgrade from Debian 10 to Debian 11. For me, removing all the .texlive* directories from my home folder solved it
mv ~/.texlive* /tmp # If you want to restore them later
rm -r ~/.texlive* # If you are sure about deleting
The ~/.texlive2020 directory was rebuilt after running pdflatex.
Excuse my ignorance as I am still getting comfortable with adding folders to paths. That being said my yeoman generators are being installed to ~/.node/lib/node_modules and ran my /usr/local/lib/node_modules.
How can I change where my yo generators install? Or how to can I add them to my yeoman path?
I just manually dragged them to the other folder
After successfully creating, building, and emulating Cordova's Hello World project, I unzipped the project folder that I am taking over from another developer on a different machine and saved it locally. While I can run the iOS app from XCode with the built project from the previous developer, I can't run the $ cordova build ios command successfully to rebuild it on my machine.
It give the following output:
The following build commands failed:
Check dependencies
Write auxiliary files
When I run it in debug mode, I notice that both of these commands are trying to make a directory for the old dev's computer (/Users/hisName/whereHePutIt/CordovaProject/stuffItIsTryingToBuild) rather than one relative to my project folder (/Users/myName/whereIPutMine/CordovaProject/stuffItIsTryingToBuild).
There is a lot of text to comb through, but it looks as though it is always failing while attempting to make a directory in /Project/platforms/ios/CordovaLib/build/CordovaLib.build
I am really stumped by this because I can't find any sort of setting or file in the project that tries to write anywhere but a path relative to my project file, and Android builds and emulates fine.
I had a similar issue on Android actually. My home for sdk tools moved but the project still wanted to use the old sdk tools.
The solution I took was to remove the platform and then re-add it. I am sure there is a way of going through the existing files and patching this, but everything you should need is in the plugin/ and www/ and where ever you elected to keep your assets.
If you do try this, make sure to create a backup before removing the platform -- it would be awful to lose changes that someone might have jammed down in the platform/ios folder.
I just ran across this issue under similar circumstances - unzipped a zipped copy of a iOS Cordova app from a coworkers computer to continue developing it, and found I could not successfully run the cordova build command.
I managed to get this to work by deleting the old "Debug-iphonesimulator" folders that had been zipped up with the rest of the project from the other computer, and then re-running the build command.
There were two folders that I deleted:
"../ios/CordovaLib/build/CordovaLib.build/Debug-iphonesimulator"
and
"../ios/build/ProjectName.build/Debug-iphonesimulator"
Hope this helps someone!
i've been working on this for a while now but i'm still stuck. This is what i've done...
Installed Eclipse
Installed SDK, NDK
Created a project from an existing source... which i browsed to muPDF/android
Then i installed Cygwin to build the project
I used ndk-build to build the project by cygwin
Then i got an error that says ".../Downloads/mupdf-0.8.165/android/jni/mupdf.c:11:19: error: mupdf.
h: No such file or directory"
I've been finding a way to fix this but it keeps on having other new problems after and after. so i would like to ask for your help... plz
Thanks in advance... Best regards, Sirisub
In the directory above there is a script called build.sh that runs the Android.mk and other makefiles; all the locations in those makefiles are set to be run from that location.
However, there are lots of other problems, not all of which I've resolved yet; quick hints, though, you need the third-party libs like jpeg and so on in a directory called "thirdparty" in the same source location as the rest of mupdf (so as siblings of the android subdirectory) and some of the libs need you to produce config headers to make everything work!
I'm currently trying to work out how to link it all ....