https://github.com/thought-machine/please-intellij/issues
e.g stuff like this:
def package():
passI've assumed that default_visibility arg is gone, but removing it will break stuff
btw, is this a plugin bug or i'm doing it wrong?
filegroup(
name = "system_proto",
srcs = [
"system_proto.build_defs",
],
visibility = ["PUBLIC"],
)
subinclude(':system_proto')
system_get_protoc_tool(
name = "protoc.fetched",
version = "3.15.4",
)I'm including the build_defs and using it in the same scope to setup targets with default versions. ide can't recognize the system_get_protoc_tool function
6 replies
23 replies
no buildable Go source files in <path>/github.com_davecgh_go-spew#dl_build/github.com/chzyer/test/test.go, line 16, column 2: can't find import: "github.com/chzyer/logex"
Hi all,
I use Please within Node.js so I use WebStorm.
I tried to install this plugin https://plugins.jetbrains.com/plugin/16816-please but I got next error:
Plugin 'Please' requires plugin 'com.intellij.modules.python' to be installed
I took a look if it's possible to enable Python support in WebStorm but I figured out that it isn't supported and it isn't even planned to support Python.
So I have a question. Is it planned to add supporting WebStorm.
Thank you.
2 replies
Example structure:
repo1/.plzconfigrepo1/BUILDrepo2/BUILDrepo2/greeting.txt
repo1/BUILD:
local_repository(
name = 'repo_2',
path = '../repo2',
)repo2/BUILD:
export_file(
name = 'greeting',
src = 'greeting.txt',
)repo2/greeting.txt:
Hello Please!Using:
$ cd repo1
$ plz build ///repo_2//:greeting
$ cat $(plz query output ///repo_2//:greeting)
Hello Please!
setup.pydid things and was curious on the preferred the way to generate a bdist with Please.
4 replies
14 replies
Hey all! I've posted a discussion around how we are going to support third party plugins for Please going forward:
https://github.com/thought-machine/please/discussions/1843
By plugin I just mean a repo that provides build definitions for a language or technology e.g. C# or terraform
Let me know what you think of this approach.
I'm currently using meson for my personal monorepo (mostly C++), and trying to switch to please. I happen to have some hundreds of dependencies to libraries installed in my system (all discoverable through pkg-config), and I wonder what would be the best way to migrate them?
- As far as I understand, there's no way to use system libraries in please, and it's better to either build from source (looking up online repos with sources and writing BUILD files is not what I'm looking for to do for more than a couple of libs), ...
- ...or copy .so / .h files into my repository and write BUILD files to link them.
Assuming that that item 2 is not completely insane, I have another question:
- I don't want to put those .h files to the root of my repo, ideally they should be in /third_party/library_name/*.h. However, as one library usually has many .h files and they often reference each other using absolute paths, I have to edit those manually and add /third_party/library_name/ to all such #include's.
Isn't there a way to make please add-Ithird_party/library_nameto C++ compiler for all C++ rules depending on that library?
As far as I understand, there's no way to use system libraries in please
I don't think this is true. Please will find system libs in the standard locations (more accurately clang and gcc will). You can pass more system library locations through the cc flags config options:https://please.build/config.html#cpp
Cpp.PkgConfigPath
"please build nextjs" but it returns generic results. 😅 Is there a tag we can use to make it more specific? (for example, using"golang" instead of just plain "go")
1 reply
I don't think this is true. Please will find system libs in the standard locations (more accurately clang and gcc will). You can pass more system library locations through the cc flags config options:https://please.build/config.html#cpp
I think this describes the global C++ options, but I'd like it to work "automatically", e.g. if I list //third_party/tensorflow:tensorflow_cc (or whatever) as a dependency to my library, then linker does -ltensorflow_cc -ltensorflow_framework -L/usr/lib when the binary depending on it is linked.
With global override of linker options, all I can do is list all external libraries there, and then all my target will be linked against 200 libraries that I use (in different projects of one repo)
17 replies
Is there a way to query please to get a rule particular file is part of?
E.g if there's cc_library( name="blah", srcs=['a.cc']) then please query <something> path/to/a.cc would return //foo/bar:blah?
Only need that for cc_library and cc_binary, only for .cc (and .h in hdrs as a bonus).
Need it for "Compile the file I'm editing" shortcut in IDE.
plz query whatinputs
remote_file as per the docs examples for integrating with the rust pleasings, won't work. So I've been trying to import as a github_repo, but that doesn't seem to address that the references contained inside the pleasings repo would need to be interpreted within the context of that repo, rather than the importing project. I have a feeling this is a me problem, and not a please problem.
