set up the file structure
This commit is contained in:
@ -2,4 +2,5 @@ set(PROJECT_NAME ${CMAKE_PROJECT_NAME})
|
||||
set(CMAKE_CXX_STANDARD 17)
|
||||
set(CMAKE_CXX_FLAGS "-g -O2")
|
||||
include_directories(${CMAKE_CURRENT_SOURCE_DIR}/sqlite-amalgamation-3430200)
|
||||
add_executable(casemanager casemanager.cpp sqlite-amalgamation-3430200/sqlite3.c)
|
||||
add_executable(casemanager casemanager.cpp sqlite-amalgamation-3430200/sqlite3.c)
|
||||
add_executable(judger judger.cpp)
|
@ -1,5 +1,12 @@
|
||||
/**
|
||||
* @file casemanager.cpp
|
||||
*
|
||||
* @brief this is the casemanager of ICPC-Management-System to manage the test
|
||||
* cases.
|
||||
*/
|
||||
#include <sqlite3.h>
|
||||
#include <stdio.h>
|
||||
#include <unistd.h>
|
||||
|
||||
static int callback(void *NotUsed, int argc, char **argv, char **azColName) {
|
||||
int i;
|
||||
|
8
checker/judger.cpp
Normal file
8
checker/judger.cpp
Normal file
@ -0,0 +1,8 @@
|
||||
/**
|
||||
* @file judger.cpp
|
||||
*
|
||||
* @brief this is the judger of ICPC-Management-System to test the code.
|
||||
*/
|
||||
int main(int argc,char* argv[]){
|
||||
return 0;
|
||||
}
|
39
src/main.cpp
39
src/main.cpp
@ -1,10 +1,33 @@
|
||||
/**
|
||||
* @file main.cpp
|
||||
*
|
||||
* @brief this is the main code of ICPC-Management-System
|
||||
*
|
||||
* @details .
|
||||
*/
|
||||
#include<cstdio>
|
||||
int main()
|
||||
{
|
||||
return 0;
|
||||
}
|
||||
*
|
||||
* @details In the function main(), the program will read the input data and
|
||||
* call the APIs. Then the APIs will call the detailed functions to do the real
|
||||
* work.
|
||||
*
|
||||
* @codesytle This file is written in a sytle mainly based on Google C++ Style
|
||||
* Guide. What's sepecial is the comment:
|
||||
* 1. Multi-line comments are always before the code they comment on.
|
||||
* Usually the code they comment on is a complex procedure,like the definition
|
||||
* of a function,a class or a variable with complex operation. If a multi-line
|
||||
* comment is in one line, it will start with "/*" instead of "/**",otherwise it
|
||||
* will start with "/**" and in the format of Doxygen.
|
||||
* 2. Single-line comments are always after the code they comment on.
|
||||
* Usually they are in the same line with the code they comment on,but sometimes
|
||||
* they may come in the next lines. single-line comments shouldn't exceed 3
|
||||
* lines as they are intended to be short and easy to understand.
|
||||
* 3. Temporary disabled code will be marked with "//" in the front of each
|
||||
* 4. Some comments have special meanings,like "//TODO", "//FIXME", "//XXX","//
|
||||
* clang-format off" and "// clang-format on". They are not controlled by the
|
||||
* previous rules.
|
||||
*
|
||||
* As I use Clang-format to format my code, so the code style may be a little
|
||||
* bit strange sometimes, in the case I'll manually format the code.
|
||||
*/
|
||||
#include <algorithm>
|
||||
#include <cstdio>
|
||||
#include <string>
|
||||
using namespace std;
|
||||
int main() { return 0; }
|
Reference in New Issue
Block a user