Closed GoogleCodeExporter closed 9 years ago
GoogleCodeExporter
commented
9 years ago please update to liteide x12.5, new version remove old dock window and use
idea style tool window.Original comment by Visua...@gmail.com on 17 Sep 2012 at 1:03
GoogleCodeExporter
commented
9 years ago Thanks! Downloaded, installed...
Window is still initially oversized, but maximizing works well, and puts it to
screen (menu/dock) boundaries. Resizing main window now works well too.
Opening LiteIde/preferences as to adjust options, oversize window again out of
boundaries. Not too annoying.
Restarting IDE "remembers" window size - NICE!
---- panes
resizing "Build Output" pane behaves erratically at first (keeps resizing main
window), after some toying (split/unsplit moving right/top/left) starts working
fine (resizing proprerly everywhere at any position)
Now... running issues .....
---- build and run... /Users/lj/dev/go/hello_world.go
<action id="FileRun" cmd="$(GO)" args="run $(EDITOR_NAME)"
work="/Users/lj/dev/go">
> /Users/lj/go/bin/go run hello_world.go
> error
process failed to start.
</action>
sounds great except go is
not in user dir but in /usr/local/go/
Default installation on Mac AFAIK goes to /usr/local/go/ (this was when I made
"default" installation) Some adjustment is needed namely changing GOROOT from
$HOME/go in setup/environments. Maybe some user friendly setup of go compiler?
darwin-32.env to be:
#drawin32 environment
GOROOT=/usr/local/go
GOARCH=386
GOOS=darwin
PATH=$GOROOT/bin:$PATH
LITEIDE_GDB=gdb
LITEIDE_MAKE=make
LITEIDE_TERM=/usr/bin/open
LITEIDE_TERMARGS=-a Terminal
LITEIDE_EXEC=/usr/X11R6/bin/xterm
LITEIDE_EXECOPT=-e
Otheriwise ide do not see go compiler at all...
Now, with adjusted GOROOT:
--- Projects/
projects seem to be insisting to be placed in GOROOT (in my setup GOROOT is
different than my code working root), only last option in making project
succeed: Go1 Command Project (Not Use GOPATH).
---- Build/Run (BR icon)
cannot build... problem looks to be in goexec (insisting on using ASM ...); "go
build src.go" would do fine on mac.
<action id="Build" cmd="$(GO)" args="build $(BUILDARGS)"
work="/Users/lj/dev/go/p1">
> /usr/local/go/bin/go build
#
runtime
/usr/local/go/src/pkg/runtime/asm_386.s:6 8a: No such file or
directory: zasm_GOOS_GOARCH.h
> exit code 2, process exited
normally.
</action>
Opening/Building a single file also works but creates same error message
(trying to asm) when attempt to build.
--- Run in Term (R> icon)
"Run in Terminal" insist on XTERM, it is an overkill (apart from not working),
would be better (if it can be done) to use /Applications/Utilities/Terminal.app
xterm however produce:
'''
exec: "./go": stat ./go: no such file or directory
Press enter key to continue
'''
------ Simple run (hello_world.go) from user local work folder (R icon):
<action id="Run" cmd="$(EDITOR_DIR)/$(EDITOR_DIRNAME)" args="$(TARGETARGS)"
work="/Users/lj/dev/go">
> /Users/lj/dev/go/go
> error process failed to
start.
</action>
does not pickup file name... adds extra "/go" behind file's dir.
--- file run (FR icon)
<action id="FileRun" cmd="$(GO)" args="run $(EDITOR_NAME)"
work="/Users/lj/dev/go">
> /Users/lj/go/bin/go run hello_world.go
> error
process failed to start.
</action>
do not use GOROOT ...
--- other "interesting" observations....
When opening DIR instead of file, many source.go files become dirs. Believe
this is intentional... but may be confusing. Better to be "packages".
----------
noted setup for osx term application LITEIDE_TERM= but do not know how to invoke
Hope this feedback helps.
Like new look & feel, very modern!
All the best! Cheers.
ljOriginal comment by lj011...@gmail.com on 17 Sep 2012 at 1:23
Original issue reported on code.google.com by
lj011...@gmail.comon 28 Aug 2012 at 3:19