LittlevGL - PC Simulator using Visual Studio 2017

This is a pre-configured Visual Studio project to try LittlevGL on a Windows PC. The project uses the SDL library which is copied and linked to the project, so you can compile it without any extra dependencies. The 64 bit libraries are used so it will work out-of-the-box on 64-bit systems.

Instructions for cloning, building and running the application are found below.

How to Clone

This repos contains other, necessary LittleVGL software repositories as git sub-modules. Those sub-modules are not pulled in with the basic git clone command and they will be needed. There are a couple of ways to pull in those submodules.

Everything at Once

This command will clone this top level repo and all submodules in a single step.

git clone --recurse-submodules https://github.com/littlevgl/pc_simulator_sdl_visual_studio.git

Main Repo First, Sub-modules Second

If you've already cloned the main repo you can pull in the sub-modules with a second command. Both commands are shown below.

git clone https://github.com/littlevgl/pc_simulator_sdl_visual_studio.git
cd pc_simulator_sdl_visual_studio
git submodule update --init --recursive

How To Build & Run

Open the pc_simulator_sdl_visual_studio solution file in Visual Studio. Click on the Local windows Debugger button in the top toolbar. The included project will be built and run, launching from a cmd window.

Trying Things Out

There are a list of possible test applications in the main.c file. Each test or demo is launched via a single function call. By default the demo_create function is the one that runs, but you can comment that one out and choose any of the others to compile and run.

Use these examples to start building your own application testing code inside this pc_simulator.

A Note About Versions

This repository usually has its sub-module references updated shortly after the release of new, major releases of LittlevGL's core lvgl project. If you need to pull in bug fixes in those sub-modules in between major releases you will have to update the references on your own. Be aware that if source files are added or removed in those sub-modules then the visual studio project will most likely need adjusting. See the commit log for this repo for examples of the changes needed when sub-module references are updated.