| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
|
|
|
|
| |
This reverts commit eaada771a6e62ca494a625ce1b060f1a94fa9877.
Reason for revert: Breaks build_test and other builds
Bug: 155862492
Change-Id: I1a14b84d54b05596ec250b31ae56e437cf49fd81
|
| |
|
|
|
|
|
|
| |
Remove the source and switch the OWNERS to the janitors to prevent
necromancy.
Test: treehugger
Change-Id: I85d58aafad17c65d7d2963c99409dddf8888fb16
|
| |
|
|
|
|
|
|
|
| |
GetModuleFileName() takes the maximum number of TCHARs we can
fit as the final argument, and thus we need to divide by
sizeof(TCHAR), instead of multiplying by it.
Test: Treehugger
Change-Id: Icbbb04c29955075e9341a0153dbd750cce8e884b
|
| |
|
|
|
|
|
| |
Since 'fviBuffer' was allocated with an array new, it needs to
be deallocated with an array delete.
Change-Id: I0a96ec78b0d230f64566ad16df0a58c9cdc7e043
|
|
|
In the code base we have a "find_java" directory
that compiles using mingw32 + an Android.mk; it is
used to create the find_java.dll used by the NSIS
installer, the find_java.exe that is used by android.bat
to locate java before executing the SDK/AVD Manager
and finally also used by the Android Studio WinLauncher.
This reworks find_java to create 2 new MFC apps:
- FindJava2 is a straight replacement for the previous find_java.exe.
- WinLauncher2 will be a replacement for the Studio launcher.
The main change is that the new app has a UI so it lists
all the Java.exe paths and let the user add his/her own.
Then it remembers the selected path using a registry key
and reuses the next time if it's available.
The app is built using VS2013 and MFC and there's no
Android.mk for it. The goal is to just make prebuilts
(that's how find_java.exe/dll and WinLauncher are actually
used right now.)
The FindJava2 part is final.
What's left to do:
- Merge the code of WinLauncher into WinLauncher2 to
actually run Studio (they will be a need for both a
32-bit version and 64-bit version support.)
- Create a new FindJava2.dll for NSIS once we decide how
we want to use this in the new installer (e.g. do we
just want to make sure there is "some" version of Java
or do we want to include the select-and-register functionality
too so that the user doesn't have to be asked again later?)
Change-Id: I814ed46711ac17a66cd63b9e7c7d485632169ff1
|
