I tried to remove git from my subfolder react project in my parent folder MERN project..
I tried the command rm -rf .git in my react/frontend folder but it display :
Remove-Item : A parameter cannot be found that matches parameter name
'rf'.
You seem to be using windows powershell. if that's the case, use the equivalent of "rm -rf" for powershell which would be: "rm -r -fo"
Related
I didn't understand how to give the path of the pro version in the current project
I read the setup from pub.dev but don't know how can I did it.
followed this steps : setup information
already clone a repo
facing one error here : zsh: permission denied: ./configurator.sh. while running this ./configurator.sh it will show error.
how to give path of new font repo to my project? ( in pubspec.yaml)
here is image where i stored clone repo project
$ sudo ./configurator.sh --exclude solid
$ sudo ./configurator.sh --exclude solid,brands
Give the Access to the Path
I don't know if you can use the absolute path here. But you can use the relative path to target package here.
For relative path:
Add the package somewhere in your project. Usually, all local repositories are stored in new packages folder at the root of the project (where the lib folder is located)
You'll get something like: ./packages/package_folder
For absolute path:
Copy the path to the package folder. You'll get something like Users/username/Desktop/../package_folder
if you are using MAC / M1 chip then use this command to run the file
$ cd util
$ bash ./configurator.sh --dynamic
To exclude unused styles combine the configurator options:
$ configurator.sh --dynamic --exclude solid
In Vs code whenever i open VS code application this message is pop up.
[Ycm] Invalid ycm path
What is the meaning of this message and how do i can fix this?
Hi，I have fixed this note，but looks like ycm does not work.
--
I use this link to fix.
My command have some differences.
git clone https://github.com/Valloric/YouCompleteMe.git
cd YouCompleteMe
git submodule update --init --recursive
cd third_party
mkdir ycmd_build
cmake -G "Unix Makefiles" . /Users/xx/software_cfg/ycm/YouCompleteMe/third_party/ycmd/cpp
Then copy 'ycm_core.cpython-310-darwin.so' to VS Code ycmd path.
--
After these setting，I found ycm still not work.
Just add one dir path in [Ycmd: Path], the note will disappear.
I use Atollic 8.1 which is build up upon Eclipses Neon 1a release on Windows 10.
The Clean command is by default "rm -rf" in the .cproject. When executed, the clean command removes all *.o and *.d objects im Debug/Release but not *.su files.
When comparing to newer Eclipse releases, the clean command actually is able to delete the entire Debug / Release folder (Build Outputs).
I tried to do the same by manually editing the clean command in .cproject by writing "rm -rf Debug Release", so when executed, Eclipse does something like this in the background:
"rm -rf Debug Release *.o *.d" but currently it still ignores Debug and Release.
So why are they not deleted? Then i replaced "rm -rf" with "pwd" and noticed that it is executing from inside the Debug folder.
So my .cproject executes now "rm -rf ../Debug ../Release" which is working ... kinda...
The Debug folder is completely empty, which is my goal. But:
I get the error:
C:\Program Files (x86)\Atollic\TrueSTUDIO for ARM 8.1.0\Tools\rm.exe: cannot remove directory `../Debug': Permission denied
I believe that since it executes the actual "rm -rf ../Debug" command but since it is executing from inside the Debug folder, it recreates it and issues the warning.
Is there a better way around this?
I have built a project using cmake (LLVM project) and tried to install it by issuing the following command:
$ cmake3 --build . --target install
If I run it using root then there is no problem and the files will be installed under the directory /usr/local/.
My problem is when I want to install the project using normal user.
I get the following error:
CMake Error at cmake_install.cmake:36 (file):
file INSTALL cannot set permissions on "/usr/local/include/llvm"
I have changed the permission of directory /usr/local/ to 777 recursively, and their ownership to root:wheel and I added my normal user to group wheel. But I still cannot install the files into the /usr/local/ directory.
The main issue is about building project in Eclipse which fails at "Build Install" command.
chmod 777 -R / is a very scary command. I've destroyed a system once by doing that.
The philosophy I use for this is:
If I need to deploy something through my IDE to debug or test before packaging, I deploy it locally within my home directory.
I only install stuff to my system (outside of home) if it has been packaged first (*.deb, *.rpm, *.tar.gz) so that I can remove it without problems.
For me, I do this with:
cmake $src
cmake --build . --target install -- DESTDIR=stage
This will configure my project, make it, then install it locally in a folder called ./stage which resides in my build directory. I can then run my executable from ./stage/usr/bin. Note that this only works if make is your generator.
Once I've tested it and I'm happy, I package it and deploy to my system or upload to a repository:
cpack
sudo dpkg -i <package>.deb
We should use USE_SOURCE_PERMISSIONS in our install function.
Example:
install(DIRECTORY "${CMAKE_CURRENT_BINARY_DIR}/Release/" DESTINATION "${CMAKE_CURRENT_BINARY_DIR}" USE_SOURCE_PERMISSIONS)
octave:1> doc fflush
info: /usr/local/Cellar/octave/3.6.3/share/info/octave.info: No such file or directory
I'm not sure what I've done wrong with my installation, but I get the msg above when attempting to find the documentation (help fflush works fine). Does anyone know how to fix this issue?
I had the same problem and solved it with manually decompressing the corresponding deb archive to the respective place of the brew installation:
Download the deb from here : http://packages.ubuntu.com/de/quantal/all/octave-info/download
cd ~/Downloads
mkdir doc
cd doc
ar -x ../octave-info_3.6.2-5_all.deb
tar xzf data.tar.gz
cd usr
find . -name '*.gz' -type f -exec gunzip "{}" \;
cd ..
cp -r share /usr/local/Cellar/octave/3.6.4/
cd ~/Downloads
rm -r doc
You have to adjust the octave version numbers to match the most recent and your brew cellar of course.
I don't know about Mac OSC. If you had built it yourself, could have been that you disabled the documentation at build time. With a package manager... you already checked that it does not have a separate octave-doc package.
There's a bunch of other package managers for Mac that have Octave. See Octave's wiki. Taking a quick look at the other package managers, it seems that they all have separate packages for docs.