How to fix goprefix/importpath to support my project structure?
I have the following project structure:
proj
---| folder1
------------| stuff1
--------------------| stuff1.go
------------| stuff2
--------------------| stuff2.go
---| folder2
------------| stuff1
--------------------| stuff1.go
------------| stuff2
--------------------| stuff2.go
....
---| app.go
Which ends up generating import paths like:
import folderOneStuff github.com/username/proj/folder1/stuff1
import folderTwoStuff github.com/username/proj/folder2/stuff1
...
Now I try to use bazel gazelle to generate build files for me. Therefor I followed this: https://github.com/bazelbuild/bazel-gazelle#running-gazelle-with-bazel
If I now run $ bazel run //:gazelle
, I get an error stating that "go prefix is not set, so importpath can't be determined for rules." even though my BUILD file has this as the first line:
# gazelle:prefix github.com/username/proj
I assume at this point that gazelle is having problems with my folder structure, can I fix this for automated build files or do I have to manually create build files?
Is this a problem that is only solvable by changing my project structure, so rather a go project structure problem rather than a problem with me using bazel (wrong)?
go bazel
add a comment |
I have the following project structure:
proj
---| folder1
------------| stuff1
--------------------| stuff1.go
------------| stuff2
--------------------| stuff2.go
---| folder2
------------| stuff1
--------------------| stuff1.go
------------| stuff2
--------------------| stuff2.go
....
---| app.go
Which ends up generating import paths like:
import folderOneStuff github.com/username/proj/folder1/stuff1
import folderTwoStuff github.com/username/proj/folder2/stuff1
...
Now I try to use bazel gazelle to generate build files for me. Therefor I followed this: https://github.com/bazelbuild/bazel-gazelle#running-gazelle-with-bazel
If I now run $ bazel run //:gazelle
, I get an error stating that "go prefix is not set, so importpath can't be determined for rules." even though my BUILD file has this as the first line:
# gazelle:prefix github.com/username/proj
I assume at this point that gazelle is having problems with my folder structure, can I fix this for automated build files or do I have to manually create build files?
Is this a problem that is only solvable by changing my project structure, so rather a go project structure problem rather than a problem with me using bazel (wrong)?
go bazel
add a comment |
I have the following project structure:
proj
---| folder1
------------| stuff1
--------------------| stuff1.go
------------| stuff2
--------------------| stuff2.go
---| folder2
------------| stuff1
--------------------| stuff1.go
------------| stuff2
--------------------| stuff2.go
....
---| app.go
Which ends up generating import paths like:
import folderOneStuff github.com/username/proj/folder1/stuff1
import folderTwoStuff github.com/username/proj/folder2/stuff1
...
Now I try to use bazel gazelle to generate build files for me. Therefor I followed this: https://github.com/bazelbuild/bazel-gazelle#running-gazelle-with-bazel
If I now run $ bazel run //:gazelle
, I get an error stating that "go prefix is not set, so importpath can't be determined for rules." even though my BUILD file has this as the first line:
# gazelle:prefix github.com/username/proj
I assume at this point that gazelle is having problems with my folder structure, can I fix this for automated build files or do I have to manually create build files?
Is this a problem that is only solvable by changing my project structure, so rather a go project structure problem rather than a problem with me using bazel (wrong)?
go bazel
I have the following project structure:
proj
---| folder1
------------| stuff1
--------------------| stuff1.go
------------| stuff2
--------------------| stuff2.go
---| folder2
------------| stuff1
--------------------| stuff1.go
------------| stuff2
--------------------| stuff2.go
....
---| app.go
Which ends up generating import paths like:
import folderOneStuff github.com/username/proj/folder1/stuff1
import folderTwoStuff github.com/username/proj/folder2/stuff1
...
Now I try to use bazel gazelle to generate build files for me. Therefor I followed this: https://github.com/bazelbuild/bazel-gazelle#running-gazelle-with-bazel
If I now run $ bazel run //:gazelle
, I get an error stating that "go prefix is not set, so importpath can't be determined for rules." even though my BUILD file has this as the first line:
# gazelle:prefix github.com/username/proj
I assume at this point that gazelle is having problems with my folder structure, can I fix this for automated build files or do I have to manually create build files?
Is this a problem that is only solvable by changing my project structure, so rather a go project structure problem rather than a problem with me using bazel (wrong)?
go bazel
go bazel
edited Nov 14 '18 at 18:02
Shudipta Sharma
1,187413
1,187413
asked Nov 14 '18 at 17:12
DanielDaniel
11712
11712
add a comment |
add a comment |
0
active
oldest
votes
Your Answer
StackExchange.ifUsing("editor", function ()
StackExchange.using("externalEditor", function ()
StackExchange.using("snippets", function ()
StackExchange.snippets.init();
);
);
, "code-snippets");
StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "1"
;
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function()
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled)
StackExchange.using("snippets", function()
createEditor();
);
else
createEditor();
);
function createEditor()
StackExchange.prepareEditor(
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader:
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
,
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);
);
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53305489%2fhow-to-fix-goprefix-importpath-to-support-my-project-structure%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
0
active
oldest
votes
0
active
oldest
votes
active
oldest
votes
active
oldest
votes
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53305489%2fhow-to-fix-goprefix-importpath-to-support-my-project-structure%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown