In our app we are using cocoapods to keep our config file in a private repo and access the file in build phase like this
CONFIG_FILE="${PODS_ROOT}/My-Repo-Name/swiftlint.yml"
"${PODS_ROOT}/SwiftLint/swiftlint" --config $CONFIG_FILE
Now we are thinking of moving the config file to a swift package, can anyone help to determine how to give a path to the config file in the swift package?
Bit of a hack, but you might be able to use:
CONFIG_FILE="${BUILD_DIR}/../../SourcePackages/checkouts/My-Repo-Name/swiftlint.yml"
The above answer didn't work but this did
CONFIG_FILE="${BUILD_DIR%Build/*}SourcePackages/checkouts/<repo-name>/Sources/swiftlint.yml"
Related
I've added a file extension to the ignore.conf but I marked the "Apply rule for all workspaces" and that adds it to another ignore.conf file that's not in my repository.
I'm on macOS and I can't find where that global ignore is. Googling found it for Windows but not for macOS.
Any ideas?
I guess you don't have a "plastic-global-config" repo so the client configuration in a macOS should be found in the following paths:
/Users/xxx/.plastic4/ignore.conf
or
/Applications/PlasticSCM.app/Contents/MonoBundle/ignore.conf
I'm trying to switch over my current setup for Neovim (using Vim Plug) to Packer and I'm having trouble.
My Neovim is loaded from ~/.config/nvim/init.lua which sources all of my plugin and other settings. They live mostly inside of a ~/lua folder (the "main Imports") section of my configuration, including my actual plug-plugins.lua file that references all of my plugins.
-- Main Imports
require("settings")
require("colors")
require("mappings")
require("functions")
require("autocommands")
require("plug-plugins")
...
Later in the same init.lua file, I'm sourcing plugin specific settings for all of these plugins. In order to get my directory working currently, I'm installing everything with :PlugInstall and it works fine.
...
-- Plugin-specific settings
require("plugin-settings/fzf")
require("plugin-settings/fugitive")
require("plugin-settings/ultisnips")
require("plugin-settings/coc")
require("plugin-settings/treesitter")
require("plugin-settings/miscellaneous")
require("plugin-settings/toggle-terminal")
Installing Packer
The installation steps for Packer are pretty sparse, and merely state that you should clone the repository to somewhere in your "packpath" but I'm not really clear what that means. When I'm inside Neovim, and I press :set packpath? I get the following paths:
packpath=~/.config/nvim,/etc/xdg/nvim,~/.local/share/nvim/site,/usr/local/share/nvim/site,/usr/share/nvim/site,/usr/local/Cellar/neovim/HEAD-b74916c_1/share/nvim/runtime,/usr/local/Cel
lar/neovim/HEAD-b74916c_1/lib/nvim,/usr/share/nvim/site/after,/usr/local/share/nvim/site/after,~/.local/share/nvim/site/after,/etc/xdg/nvim/after,~/.config/nvim/after
This makes me think that I'm able to just clone the respository to ~/.config/nvim which is the first path listed. I'm not really sure what to do next though, or if this is even right.
Can anyone help? What are the basic steps to getting Packer installed (I'm on MacOS 11.6).
i did recently moved from vim-plug to packer, as per docs when you do git clone of the repo the path provided in readme for installation is ~/.local/share/nvim/site/pack/packer.After successful clone you can start using packer in your plugins.lua as below.
return require('packer').startup(function()
use 'wbthomason/packer.nvim'
end)
you can check the installation by running :PackerSync this will fetch (git clone) the plugin in to the packerpath which is ~/.local/share/nvim/site/pack/packer
Hope this is what you looking for?
I had the exact same situation and it turned out to just be a naming conflict. I had named my local nvim config file lua/packer.lua and changing that fixed the issue.
Instead of using .travis.yml in the root of a project, is it possible to store it in a folder called .travis or similar?
It seems that .travis.yml represents the only way to configure travis...
Check out this question and this statement
I've just built an app with Electron.
Installing and running electron-packager . creates a folder my-app-win32-x64 with a bunch of assets and DLLs.
This isn't exactly something I can distribute to consumers.
What's the simplest way to generate a Windows installer for my electron executable?
It looks like according to their wiki you can. Follow the instructions here! https://github.com/electron/windows-installer
You may try electron-wix-msi it will help you to create a exe file.
it will basically ask you for your source file Path example D:\xyz\my-app-win32-x64
and will create a desired file at app source path.
I'm new at iOS development, and I want to run this project https://github.com/google/uribeacon/tree/master/ios-uribeacon
that I thought it should work out of the box.
I've tried to build and run uribeacon-sample, but I can't because I got this error 'MBProgressHUD/MBProgressHUD.h' file not found
I 've seen that there this this project https://github.com/jdg/MBProgressHUD, but I don't know how to include it
when you clone your git, need to get submodules;
git clone --recursive git://github.com/foo/bar.git
You can also follow the MBProgressHUD instructions and use CocoaPods, It's very simple to use and you can use it to add, not only this one but, multiple open source projects to your own code.