Project Austin

Updated Wiki: Build Instructions

GeorgeMileka — Thu, 06 Jun 2013 00:46:15 GMT

Project Austin is a Windows Store application for taking notes.

To build and run this application, follow these steps:

Get the latest Source Code
1. Download the latest .zip file from here.
2. Unzip the file to the project root folder (It can be any folder of your choice. We'll refer to it as <project root>.).
Install the Project Code Name Austin Libraries. The Project Code Name Austin Libraries are a set of dlls and libraries necessary for the application to run. To obtain the libraries:
1. Review the license terms for the Project Code Name Austin Libraries located in license.rtf.
2. Download austin_libraries_neutral.zip.
3. Download austin_libraries_x64.zip.
4. Download austin_libraries_x86.zip.
5. Download austin_libraries_ARM.zip.
6. Unzip all three files to '<project root>\dependencies'.
Install the boost Library 1.47
1. Navigate to the boost library version 1.47 at its official release point.
2. Download boost147_0.zip.
3. Unzip boost1470.zip to 'c:\temp\boost1470'.
4. Copy the contents of 'c:\temp\boost147_0\boost' to '<project root>\sdk\inc\boost'
Install dbghelp (needed only if you intend to build the Win32 debug flavor of the project)
1. Launch the Windows 8 SDK. Navigate to this page and click 'download'.
2. Follow the prompts until the screen where you can select what to install.
3. On the screen, make sure the 'Debugging Tools for Windows' component is selected, and then start the installation. Note: The rest of the components are optional to the purpose of building and running 'Project Austin'.
4. Copy "C:\Program Files (x86)\Windows Kits\8.0\Debuggers\inc\dbghelp.h" to "<project root>\sdk\inc\"
5. Copy "C:\Program Files (x86)\Windows Kits\8.0\Debuggers\lib\x86\dbghelp.lib" to "<project root>\sdk\lib\debug\"
6. Copy "C:\Program Files (x86)\Windows Kits\8.0\Debuggers\x86\dbghelp.dll" to "<project root>\sdk\bin\debug\"
Verify the tree structure
1. The directory structure under '<project root>' should look like this:

    baja
    baja.props
    dependencies
        hlsl
        includes
        x64
        x64_debug
        x86
        x86_debug
    journal
    journal.sln
    sdk
        bin
        inc
        lib

6. Open journal.sln in Visual Studio 2012 to build and run.

Updated Wiki: Build Instructions

GeorgeMileka — Thu, 06 Jun 2013 00:17:49 GMT

Project Austin is a Windows Store application for taking notes.

To build and run this application, follow these steps:

Get the latest Source Code
1. Download the latest .zip file from here.
2. Unzip the file to the project root folder (It can be any folder of your choice. We'll refer to it as <project root>.).
Install the Project Code Name Austin Libraries. The Project Code Name Austin Libraries are a set of dlls and libraries necessary for the application to run. To obtain the libraries:
1. Review the license terms for the Project Code Name Austin Libraries located in license.rtf.
2. Download austin_libraries_neutral.zip.
3. Download austin_libraries_x64.zip.
4. Download austin_libraries_x86.zip.
5. Download austin_libraries_ARM.zip.
6. Unzip all three files to '<project root>\dependencies'.
Install the boost Library 1.47
1. Navigate to the boost library version 1.47 at its official release point.
2. Download boost147_0.zip.
3. Unzip boost1470.zip to 'c:\temp\boost1470'.
4. Copy the contents of 'c:\temp\boost147_0\boost' to '<project root>\sdk\inc\boost'
Install dbghelp (needed only if you intend to build the Win32 debug flavor of the project)
1. Launch the Windows 8 SDK. Navigate to this page and click 'download'.
2. Follow the prompts until the screen where you can select what to install.
3. On the screen, make sure the 'Debugging Tools for Windows' component is selected, and then start the installation. Note: The rest of the components are optional to the purpose of building and running 'Project Austin'.
4. Copy "C:\Program Files (x86)\Windows Kits\8.0\Debuggers\inc\dbghelp.h" to "<project root>\sdk\inc\"
5. Copy "C:\Program Files (x86)\Windows Kits\8.0\Debuggers\lib\x86\dbghelp.lib" to "<project root>\sdk\lib\debug\"
6. Copy "C:\Program Files (x86)\Windows Kits\8.0\Debuggers\x86\dbghelp.dll" to "<project root>\sdk\bin\debug\"
Verify the tree structure
1. The directory structure under '<project root>' should look like this:

    baja
    baja.props
    dependencies
        hlsl
        includes
        x64
        x64_debug
        x86
        x86_debug
    journal
    journal.sln
    sdk
        bin
        inc
        lib

6. Open journal.sln in Visual Studio 2012 to build and run.

Source code checked in, #19874

GeorgeMileka — Thu, 06 Jun 2013 00:11:03 GMT

- Minor changes to remove dependencies on legacy Windows import libraries. - Incorporated support for building the solution for ARM. - Removed a debug hack that would allow calling desktop APIs.

New Post: Error Compiling- gdi32.lib missing

GeorgeMileka — Tue, 04 Jun 2013 01:39:15 GMT

Hi Kevinkk5,

Yes, the presence of the reference to gdi32.lib and a few other libraries was an oversight on our side. It crept into our project settings because we were using a pre-release version of Visual Studio. Those libraries are not really needed to link the project - feel free to remove them from the linker dependencies.

We will release another version with these issues fixed.

thanks,
George Mileka

New Post: Error: Unable to start Baja.lib after successfull build

GeorgeMileka — Tue, 04 Jun 2013 01:35:05 GMT

Hi Bageera,

When you hit F5 or Ctrl+F5 from within Visual Studio, Visual Studio attempts to run the 'StartUp Project' in the solution. In this case, the Baja project is marked as the StartUp. However, it does not produce an executable - instead, it produces Baja.lib. So, Visual Studio emits the error you are seeing.

To fix the problem, you need to right-click the Journal project, and select 'Set as StartUp Project'.

thanks,
George Mileka

New Post: Error Compiling- gdi32.lib missing

kevinkk5 — Sun, 13 Jan 2013 18:32:12 GMT

When i try to build the program it says gdi32.lib could not be found.

I downloaded that lib and then it says winspool.lib could not be found. But i didn´t find this lib anywhere in the web. Could you help me?

Did it work for you without any errors during the build-process?

New Post: Error: Unable to start Baja.lib after successfull build

BageeraS — Tue, 25 Dec 2012 11:24:38 GMT

Hi there,

After downloading the code and setting up the build I was able to compile an build successfully. But when I run the code I get an error popup which says " Únable to start program Baja.lib".

I am confused for I have done everything to make this work. Can anybody help.

I am using Microsoft VS express for Win8 and my os is win 8 64 bit.

Bageera

New Post: Austin on Iconia W510 - Direct X Problem

ytecs — Fri, 14 Dec 2012 14:13:07 GMT

Hi George,

altough the ARM version is - well, ARM, i was able to compile it by just copying the x86 dependencies to the project folder and changing the build settings to x86. Austin runs, but slow, and crashes often.

The x86 version doesn't run. I guess, the GMA 3650 has no driver supporting DirectX feature level higher than 9, but not sure and stil figuring out where the problem could be.

Oh, and no, its not the Lenovo W510, it's the Acer Iconia W510. Posting here if I'm sure where the problem with DirectX is. The Card should be able to do feature level 10, DirectX ist installed. Investigating...

Greetings,

ytecs

New Post: ARM version

GeorgeMileka — Tue, 11 Dec 2012 19:44:24 GMT

Hi mullen,

Yes, the issues I've fixed were all related to downgrading from DirectX 11 to 9.1. The texture loading errors were usually fixed by making sure the mipmap level is 1.

thanks,

George Mileka

New Post: ARM version

mullen — Tue, 11 Dec 2012 04:29:17 GMT

I think it's related to DirectX, maybe some parts still try to use DX11, which is not supported on ARM
My test: (on surface rt)

At the very beginning, charm bar, options, general, show input icon, switch it so I can draw by finger
Then, draw something, try to bring the appbar, but freezed (I didn't identify where)

Restart the app.
Bring the appbar, swith to eraser, try to erase, break here

  austin.exe!baja::bajaThrow<baja::win32_error>(const baja::win32_error & e, const char * file, unsigned int line, const char * etype) Line 138 C++
  austin.exe!baja::win32_result::setHr(HRESULT hr, const bool noThrow) Line 129 C++
  austin.exe!baja::win32_result::win32_result(const HRESULT hr) Line 68 C++
  austin.exe!baja::graphics::dx11_1::details::createTexture2DObject(ID3D11Device * d3d11Device, const unsigned int width, const unsigned int height, const unsigned int mipLevels, const baja::graphics::pixel_format format, const unsigned int msaaCount, const unsigned int msaaQualityLevel, const D3D11_USAGE usage, const unsigned int binding, const unsigned int cpuAccess, const unsigned int miscFlags) Line 802 C++
> austin.exe!baja::graphics::dx11_1::engine::createTexture(const unsigned int width, const unsigned int height, const unsigned int mipLevels, const unsigned int usage, const baja::graphics::pixel_format format, const baja::graphics::memory_pool pool, const unsigned int msaaCount, const unsigned int msaaQuality) Line 263 C++
  ink_renderer.dll!5ea01776() Unknown
  ink_renderer.dll!5ea02032() Unknown
  austin.exe!journal::view::ink_surface::renderToIdsCache() Line 84 C++
  austin.exe!journal::view::ink_surface::selectTool(journal::view::ink_surface_tool tool) Line 148 C++
  austin.exe!journal::view::page::onSelectInkTool(journal::view::ink_surface_tool tool) Line 1781 C++
  austin.exe!journal::view::notebook::onCommand(const journal::view::command_id id, void * context) Line 3315 C++
  austin.exe!journal::root::onCommand(const journal::view::command_id id, void * context) Line 465 C++
  austin.exe!journal::journal_app::onCommand(const journal::view::command_id id, void * context) Line 786 C++
  austin.exe!journal::page::clickEraser() Line 586 C++
  austin.exe!`Windows::UI::Xaml::RoutedEventHandler::RoutedEventHandler<journal::page,void (__cdecl journal::page::*)(Platform::Object ^,Windows::UI::Xaml::RoutedEventArgs ^)>'::`3'::__abi_PointerToMemberWeakRefCapture::Invoke(Platform::Object ^ __param0, Windows::UI::Xaml::RoutedEventArgs ^ __param1) C++
  austin.exe!Windows::UI::Xaml::RoutedEventHandler::Invoke(Platform::Object ^ __param0, Windows::UI::Xaml::RoutedEventArgs ^ __param1) C++
  austin.exe!Windows::UI::Xaml::RoutedEventHandler::[Windows::UI::Xaml::RoutedEventHandler::__abi_IDelegate]::__abi_Windows_UI_Xaml_RoutedEventHandler___abi_IDelegate____abi_Invoke(Platform::Object ^ __param0, Windows::UI::Xaml::RoutedEventArgs ^ __param1) C++
  Windows.UI.Xaml.dll!5ee8c2b6() Unknown
  Windows.UI.Xaml.dll!5ef8918c() Unknown
  Windows.UI.Xaml.dll!5f039456() Unknown
  Windows.UI.Xaml.dll!5ef87ff6() Unknown
  Windows.UI.Xaml.dll!5ef88840() Unknown
  Windows.UI.Xaml.dll!5ed858ca() Unknown
  Windows.UI.Xaml.dll!5ef896a8() Unknown
  Windows.UI.Xaml.dll!5ee92a5e() Unknown
  Windows.UI.Xaml.dll!5ee92c68() Unknown
  Windows.UI.Xaml.dll!5ec7c89a() Unknown
  Windows.UI.Xaml.dll!5ec7c7fa() Unknown
  Windows.UI.Xaml.dll!5ec93566() Unknown
  Windows.UI.Xaml.dll!5ec930b4() Unknown
  Windows.UI.Xaml.dll!5ec92fb2() Unknown
  Windows.UI.Xaml.dll!5ecd9166() Unknown
  user32.dll!75cf304c() Unknown
  user32.dll!75d1d3ce() Unknown
  user32.dll!75cfcaf8() Unknown
  ntdll.dll!77a7f376() Unknown
  user32.dll!75d038b6() Unknown

As I tried in release mode, copy/paste, or change background, may also crash the app.

New Post: ARM version

GeorgeMileka — Mon, 10 Dec 2012 19:30:10 GMT

Hi mullen,

Any chances you could share where it breaks when run under the debugger?

thanks,

George Mileka

New Post: Austin on Iconia W510 - Direct X Problem

GeorgeMileka — Mon, 10 Dec 2012 19:27:20 GMT

Hi ytecs,

I haven't seen this behavior before.

When you run dxdiag, on the Display tab, what does the 'Feature Levels' say?

The Austin project does not require DirectX Feature Level 11. However, it requires DirectX 11 to be present on the machine. Any machine running Windows 8 should have DirectX 11 present.

The Austin project for x86/x64 require DirectX Feature Level 10 or higher.

When Austin is run under the debugger, where does it break?

The ARM patch should not help in your scenario since the W510 is not ARM-based (I assume it's the Lenovo W510). Also, we did not do as much testing on the ARM version as what we did for the x86/x64, so I wouldn't recommend using the ARM version unless you want to explore performance on an ARM device.

thanks,

George Mileka

New Post: Austin on Iconia W510 - Direct X Problem

ytecs — Sun, 09 Dec 2012 19:35:23 GMT

Hello,

I'm trying to get Austin working on my W510. The problem is: I can compile, but then the app hangs. After a couple of time it says "Direct X 11 is needed", altough Direct X11 is properly installed.

Theres a patch for ARM, where the Direct X dependency is lowered to 9, but my x86 can't run it. What changes need to be done in the x86 version to lower the DX dependency or, vice versa, what changes does the ARM version need to run on 86? Or, better: How can Austin recognize the installed DX11 properly?

There's no other good inking app out there!

Thanks in advance

New Post: ARM version

mullen — Sun, 09 Dec 2012 10:38:02 GMT

Thank you for the ARM version. I can compile and deploy it on surface. However, it's very unstable, crashes very often. I'm not sure what's the reason. Maybe I will provide more details later.

New Post: Warnings related to dxtex.lib

GeorgeMileka — Sat, 08 Dec 2012 04:12:29 GMT

Hi Sanjeev,

Those warnings can be ignored as they will not affect the runtime behavior in any way. Those warnings show up because we have not distributed the .pdb files for the static libraries we are using.

thanks,

George Mileka

New Post: Stacks?

GeorgeMileka — Sat, 08 Dec 2012 04:09:50 GMT

Hi kallanreed,

These are great ideas - I wish we implemented them. Early on, we considered the scenario of organizing the pages - and we had it on our radar for sometime. But as the project went on, we realized we would not have enough time to implement it :(

thanks,

George Mileka

New Post: ARM version

GeorgeMileka — Sat, 08 Dec 2012 04:03:52 GMT

I forgot to mention that the modified project can be downloaded if you go to Source Code -> Patches.

New Post: Source code extension?

GeorgeMileka — Sat, 08 Dec 2012 04:02:49 GMT

rkguy wrote:

I am working on a project that involves stylus input that focuses on letter writing. I would like to extend your tool for a really novel application. Am I allowed to use it for my needs under it's current license?

I also tried contacting you through BizSpark to see if you were interested in applying my concepts to your product. No dice. In any event, PM me if you are even slightly interested. I'm not in this for the $ as much as I want to see some awesome applications to take advantage of the stylus and it'll take me a month of Sundays to do it by myself.

Hi rkguy,

The license allows people to re-use the code, add their own value, and publish it. So, feel free to extend the project. Note that the ink part is not open source though. We are distributing the ink binaries under a more restricted license. The ink part will need to be replaced with your implementation as necessary.

Let us know if you need help.

thanks,

George Mileka

New Post: ARM version

GeorgeMileka — Sat, 08 Dec 2012 03:56:50 GMT

Mullen wrote:

I tried to compile the project on ARM platform but failed. Does this project support

ARM now? If not, will it support ARM later?

Hi Mullen,

We have just uploaded a version of the Austin project that works for ARM devices. Please, let us know if you see issues building or deploying it. I think it needs some profiling/optimization - but it should work nonetheless.

thanks,

George Mileka

Patch Uploaded: #13411

GeorgeMileka — Sat, 08 Dec 2012 03:51:39 GMT

GeorgeMileka has uploaded a patch.

Description:
Based on a few requests we got, we are uploading a modified version of the Austin project that works for ARM devices. The main difference is to get the Austin project to target DirectX feature level 9.1.