Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

appengine support? #1

Closed
levb opened this issue Dec 30, 2011 · 2 comments
Closed

appengine support? #1

levb opened this issue Dec 30, 2011 · 2 comments
Assignees

Comments

@levb
Copy link

levb commented Dec 30, 2011

I'd really like to use this package for my own golang application, which is running on appengine. However, as it stands it doesn't seem to compile cleanly there. Would you consider making it "easy to use" on the appengine? I'd be willing to help out if needed.

specifically, I got these errors message immediately after cloning it into my project (I am using the go appengine 1.6.1 SDK):

/Users/levb/Documents/dev/tw/github.com/the42/cartconvert/cartconvert.go:25: undefined: error
/Users/levb/Documents/dev/tw/github.com/the42/cartconvert/cartconvert.go:29: ce.Err undefined (type CartographyError has no field or method Err)
/Users/levb/Documents/dev/tw/github.com/the42/cartconvert/cartconvert.go:169: undefined: error
/Users/levb/Documents/dev/tw/github.com/the42/cartconvert/cartconvert.go:173: undefined: rune
/Users/levb/Documents/dev/tw/github.com/the42/cartconvert/cartconvert.go:192: undefined: strconv.ParseFloat
/Users/levb/Documents/dev/tw/github.com/the42/cartconvert/cartconvert.go:195: too many arguments to return
/Users/levb/Documents/dev/tw/github.com/the42/cartconvert/cartconvert.go:204: unknown CartographyError field 'Err' in struct literal
/Users/levb/Documents/dev/tw/github.com/the42/cartconvert/cartconvert.go:204: too many arguments to return
/Users/levb/Documents/dev/tw/github.com/the42/cartconvert/cartconvert.go:215: undefined: strconv.ParseFloat
/Users/levb/Documents/dev/tw/github.com/the42/cartconvert/cartconvert.go:218: too many arguments to return
/Users/levb/Documents/dev/tw/github.com/the42/cartconvert/cartconvert.go:228: unknown CartographyError field 'Err' in struct literal
/Users/levb/Documents/dev/tw/github.com/the42/cartconvert/cartconvert.go:228: too many arguments to return
/Users/levb/Documents/dev/tw/github.com/the42/cartconvert/cartconvert.go:239: undefined: strconv.ParseFloat
/Users/levb/Documents/dev/tw/github.com/the42/cartconvert/cartconvert.go:274: undefined: error
/Users/levb/Documents/dev/tw/github.com/the42/cartconvert/cartconvert.go:345: undefined: error
/Users/levb/Documents/dev/tw/github.com/the42/cartconvert/cartconvert.go:620: undefined: error
/Users/levb/Documents/dev/tw/github.com/the42/cartconvert/cartconvert.go:669: undefined: error
/Users/levb/Documents/dev/tw/github.com/the42/cartconvert/cartconvert.go:811: undefined: error
/Users/levb/Documents/dev/tw/github.com/the42/cartconvert/cartconvert.go:864: undefined: error
/Users/levb/Documents/dev/tw/github.com/the42/cartconvert/cartconvert.go:239: too many errors

2011/12/30 11:27:07 go-app-builder: Failed building app: failed running 6g: exit status 1

@levb
Copy link
Author

levb commented Dec 30, 2011

never mind, just realized that there were all these changes in the golang that have not yet made it to the app engine SDK. I am going to temporarily bastardize your code just to stub things out, and then try again when the November release of golang is available on the appengine

@the42
Copy link
Owner

the42 commented Dec 30, 2011

Hi,

you have two options:

  1. The one you sketched. The current state of golang is almost Go 1 as of
    https://docs.google.com/document/pub?id=1ny8uI-_BHrDCZv_zNBSthNKAMX_fR_0dc6epA6lztRE&pli=1

You can expect appengine to gain soon support for Go 1. There is no official nor preliminary deadline for this. The current cartconvert package is Go 1 ready.

  1. You can travel back in time and checkout including commit 8527955 (update to weekly.2011-06-02)

This version should be save for appengine golang V3.

I would recommend #1. Anyway, you can expect the current golang-versions to be phased you relatively quickly.

@ghost ghost assigned the42 Dec 30, 2011
@the42 the42 closed this as completed Dec 30, 2011
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants