CompanyGateways / mytracks

Automatically exported from code.google.com/p/mytracks
1 stars 0 forks source link

Development process Issue #470

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago

I've made the MyTracks project compile by doing this.

1. Import MyTracks, MyTracksLib project.

2. In MyTracks project, I fixed the build path of MyTracksLib_src to absolute 
path of MyTracksLib/src folder.

3. And I fixed the protobuf-java-2.3.0-lite.jar path which is in Java Build 
Path/Libraries preference to the absolute path of 
MyTracksLib/libs/protobuf-java-2.3.0-lite.jar

4. After that, in MyTracks project's properties/Android/Library, I added 
MyTracksLib project to it.

I double checked about this, and I found out I should do all of this.
I don't know why, but I had to.

It must be the reason by the difference of development environment, I guess.
For reference, mine is this..

* eclipse
Version: Helios Service Release 2
Build id: 20110218-0911

* android SDK tools revision 11

* java
Version: 1.6.0_24

* Mercurial Distributed SCM
Version : 1.8.3

Original issue reported on code.google.com by jacobcho...@gmail.com on 24 May 2011 at 5:42

GoogleCodeExporter commented 9 years ago
I am not sure what the bug is here.  You should not need to set the absolute 
paths. In fact when you send code for reviews we will make you revert that 
change.

Original comment by sandordo...@google.com on 24 May 2011 at 5:51

GoogleCodeExporter commented 9 years ago
You are right. All I had to do additionally at development process description 
is importing MyTracksLib project.
That's all. I think it has to be described in development process, I guess.
Thank you, Sandordo.

Original comment by jacobcho...@gmail.com on 24 May 2011 at 6:17

GoogleCodeExporter commented 9 years ago

Original comment by sandordo...@google.com on 10 Jun 2011 at 3:18