Error then import local packages

[GoogleCodeExporter]

Error then import local packages

[GoogleCodeExporter]

UPD: a.a lies in ./pkg

Original comment by aka.spin on 16 Oct 2010 at 2:05

[GoogleCodeExporter]

Can you attach an example project?

Original comment by [email protected] on 20 Oct 2010 at 1:27

[GoogleCodeExporter]

In attach.

Original comment by aka.spin on 20 Oct 2010 at 5:16

• Added labels: Priority-High
• Removed labels: Priority-Medium

Attachments:

• go-example.zip

[GoogleCodeExporter]

We're actually in the process of reworking the build process to incorporate the 
concept of local packages without the use of the import "./a" construct.  You 
can weigh in here:  
http://groups.google.com/group/goclipse/browse_thread/thread/585a79ad4b941a18

Original comment by [email protected] on 22 Oct 2010 at 4:46

[GoogleCodeExporter]

Not until I read your Readme.md file I understood the issue. Until then, I was 
just trying to mimic your problem and it worked, without actually packaging 
stuff into an archive.

The issue is that you can't use import "./a" once you packaged "a".
Indeed you can keep a.a in the obj folder, but the import in main.go should be 
import "a"

The "./a" notation works for as long the package is in developing meaning the 
sources and obj's are there. Once you package it, it is a regular package. The 
fact that you install it in the distribution or keep it in the obj folder does 
not affect this.

Hope this solves the issue.

Original comment by [email protected] on 30 Oct 2010 at 11:31

[GoogleCodeExporter]

Hmm. It's not good idea. For example, if I need a service with a variety of 
data handlers, I will make central "router" and handlers. And naturally, I want 
to isolate each router in own package. Note that the main work will be in these 
packages. Also note that all packages with handlers are not required anywhere 
else. These packages only polluting the global space. Also in Go all libs has 
static linking. So. I change handler... Recompile it, repackage... Recolpile 
dependent... 

But it does not matter. I have decided to postpone it for a year at least. Go 
only initially seem nimble ... Until you start to handle complex structures 
such as JSON. Plus very strange and rigid major developers. The last straw was 
the fact that GC does not return the memory to the operating system. Until that 
Go-way is very crooked.

Original comment by aka.spin on 30 Oct 2010 at 1:54

[GoogleCodeExporter]

The latest work on the build system changed that. Now packages are 
automatically compiled and packed into .a files. You still need and I think 
should refer to packages as import ("packname") and not import ("./packname"). 
The ./ is really only for fast development without any packaging. At least this 
was my initial understanding (although it may be outdated, I admit)
The new build system will do the packaging automatically for you so no worries 
there. You can skip the ./ stuff.

Original comment by [email protected] on 6 Nov 2010 at 5:25

[GoogleCodeExporter]

Original comment by [email protected] on 7 Apr 2012 at 7:00

• Changed state: Fixed

[GoogleCodeExporter]

I am on Windows 7, Eclipse Juno (latest) with latest GoClipse plugin (0.7.2). I 
found the builder is complaining about not being able to find a local package 
(mysql_classic). I tried moving the corresponding db.go file to different 
places - but it still can't find the package. Am I doing something wrong? I see 
that the .a file is getting generated in the pkg\windows-386 folder. Why is the 
builder not getting the package?

Original comment by [email protected] on 28 Aug 2012 at 12:39

Attachments:

• goclipse_cant_find_local_pkg.png