Initial entry.

cmake_minimum_required(VERSION 3.10)

project(gensync)

set(CMAKE_CXX_STANDARD 17)

# if compiled with RECORD, GenSync server and client produce extensive log files

# that can be used to reproduce exact sync behavior afterwards

add_definitions(-DRECORD=".gensync")

include(CTest)

include(GNUInstallDirs)

# include Apache Data Sketches as a header-only library

include_directories(gensync-core/incubator-datasketches-cpp/common/include

                    gensync-core/incubator-datasketches-cpp/hll/include

                    gensync-core/incubator-datasketches-cpp/fi/include)

# some flags

set(CMAKE_CXX_FLAGS "-std=c++${CMAKE_CXX_STANDARD} -DDEFAULT_LOGLEVEL=TEST")

# Set project directory structure

set(ROOT_DIR gensync-core)

set(SRC_DIR ${ROOT_DIR}/src)

set(AUX_DIR ${SRC_DIR}/Auxiliary)

set(DATA_DIR ${SRC_DIR}/Data)

set(COMM_DIR ${SRC_DIR}/Communicants)

set(SYNC_DIR ${SRC_DIR}/Syncs)

set(BENCH_DIR ${SRC_DIR}/Benchmarks)

set(TOOLS_DIR ${SRC_DIR}/Tools)

set(TESTS_DIR ${ROOT_DIR}/tests)

set(UNIT_TESTS_DIR ${TESTS_DIR}/unit)

set(SYS_TESTS_DIR ${TESTS_DIR}/sys)

set(INCLUDE gensync-core/include/GenSync)

set(AUX_DIR_INC ${INCLUDE}/Auxiliary)

set(DATA_DIR_INC ${INCLUDE}/Data)

set(COMM_DIR_INC ${INCLUDE}/Communicants)

set(SYNC_DIR_INC ${INCLUDE}/Syncs)

set(SYNC_BENCH_INC ${INCLUDE}/Benchmarks)

# Set file config

set(SOURCE_FILES

        ${AUX_DIR}/Logger.cpp

        ${AUX_DIR}/UID.cpp

        ${AUX_DIR}/SyncMethod.cpp

        ${AUX_DIR}/Sketches.cpp

        ${DATA_DIR}/DataObject.cpp

        ${COMM_DIR}/CommSocket.cpp

        ${COMM_DIR}/CommString.cpp

        ${COMM_DIR}/Communicant.cpp

        ${COMM_DIR}/CommDummy.cpp

        ${SYNC_DIR}/CPISync.cpp

        ${SYNC_DIR}/GenSync.cpp

        ${SYNC_DIR}/InterCPISync.cpp

        ${SYNC_DIR}/probCPISync.cpp

        ${SYNC_DIR}/HashSync.cpp

        ${SYNC_DIR}/IBLT.cpp

        ${SYNC_DIR}/IBLTMultiset.cpp

        ${SYNC_DIR}/IBLTSync.cpp

        ${SYNC_DIR}/IBLTSync_Multiset.cpp

        ${SYNC_DIR}/IBLTSetOfSets.cpp

        ${SYNC_DIR}/Compact2DBitArray.cpp

        ${SYNC_DIR}/Cuckoo.cpp

        ${SYNC_DIR}/CuckooSync.cpp

        ${SYNC_DIR}/FullSync.cpp

	    ${SYNC_DIR}/BloomFilter.cpp

	    ${SYNC_DIR}/BloomFilterSync.cpp

        ${BENCH_DIR}/Runner.cpp

        ${BENCH_DIR}/BenchParams.cpp

        ${BENCH_DIR}/FromFileGen.cpp

        ${TOOLS_DIR}/EncodeJoin.cpp

        ${SRC_DIR}/main.cpp)

set(HEADERS

        ${AUX_DIR_INC}/Auxiliary.h

        ${AUX_DIR_INC}/ConstantsAndTypes.h

        ${AUX_DIR_INC}/Exceptions.h

        ${AUX_DIR_INC}/ForkHandle.h

        ${AUX_DIR_INC}/Logger.h

        ${AUX_DIR_INC}/SyncMethod.h

        ${AUX_DIR_INC}/UID.h

        ${AUX_DIR_INC}/Sketches.h

        ${DATA_DIR_INC}/DataFileC.h

        ${DATA_DIR_INC}/DataMemC.h

        ${DATA_DIR_INC}/DataObjC.h

        ${DATA_DIR_INC}/DataObject.h

        ${DATA_DIR_INC}/DataPriorityObject.h

        ${COMM_DIR_INC}/CommSocket.h

        ${COMM_DIR_INC}/CommString.h

        ${COMM_DIR_INC}/Communicant.h

        ${COMM_DIR_INC}/CommDummy.h

        ${SYNC_DIR_INC}/CPISync.h

        ${SYNC_DIR_INC}/CPISync_ExistingConnection.h

        ${SYNC_DIR_INC}/CPISync_HalfRound.h

        ${SYNC_DIR_INC}/CPISync_HalfRound_Hashed.h

        ${SYNC_DIR_INC}/CPISync_OneLessRound.h

        ${SYNC_DIR_INC}/FullSync.h

        ${SYNC_DIR_INC}/GenSync.h

        ${SYNC_DIR_INC}/HashSync.h

        ${SYNC_DIR_INC}/IBLT.h

        ${SYNC_DIR_INC}/IBLTMultiset.h

        ${SYNC_DIR_INC}/IBLTSync.h

        ${SYNC_DIR_INC}/IBLTSetOfSets.h

        ${SYNC_DIR_INC}/IBLTSync_HalfRound.h

        ${SYNC_DIR_INC}/IBLTSync_Multiset.h

        ${SYNC_DIR_INC}/Compact2DBitArray.h

        ${SYNC_DIR_INC}/Cuckoo.h

        ${SYNC_DIR_INC}/CuckooSync.h

        ${SYNC_DIR_INC}/InterCPISync.h

        ${SYNC_DIR_INC}/PrioCPISync.h

        ${SYNC_DIR_INC}/ProbCPISync.h

	    ${SYNC_DIR_INC}/BloomFilter.h

	    ${SYNC_DIR_INC}/BloomFilterSync.h

        ${SYNC_BENCH_INC}/BenchObserv.h

        ${SYNC_BENCH_INC}/BenchParams.h

        ${SYNC_BENCH_INC}/DataObjectGenerator.h

        ${SYNC_BENCH_INC}/RandGen.h

        ${SYNC_BENCH_INC}/FromFileGen.h)

include_directories(gensync-core/include)

# Users may need to update these paths - common locations are used

include_directories(/usr/local/include /opt/local/include)

link_directories(/usr/local/lib /opt/local/lib)

link_directories(/usr/local/lib64 /opt/local/lib64)

include_directories(${CMAKE_INSTALL_INCLUDEDIR})

link_directories(${CMAKE_INSTALL_LIBDIR})

# Add libs and executables

add_library(gensync STATIC ${SOURCE_FILES} ${HEADERS})

target_include_directories(gensync PRIVATE ${CMAKE_SOURCE_DIR}/gensync-core/include)

TARGET_LINK_LIBRARIES(gensync ntl cppunit pthread gmp)

install(CODE "FILE(REMOVE_RECURSE ${CMAKE_INSTALL_INCLUDEDIR}/gensync)") #Remove the existing GenSync library data and reinstall

install(CODE "FILE(REMOVE_RECURSE ${CMAKE_INSTALL_LIBDIR}/libgensync.a)") #Remove the existing GenSync library data and reinstall

install(TARGETS gensync LIBRARY DESTINATION ${CMAKE_INSTALL_LIBDIR} ARCHIVE DESTINATION ${CMAKE_INSTALL_LIBDIR})

install(DIRECTORY DESTINATION ${CMAKE_INSTALL_INCLUDEDIR}/GenSync) #create a new folder for GenSync inside of the system include directory

install(DIRECTORY ${AUX_DIR_INC} ${DATA_DIR_INC} ${COMM_DIR_INC} ${SYNC_DIR_INC} DESTINATION ${CMAKE_INSTALL_INCLUDEDIR}/GenSync COMPONENT devel) #copy the contents of the include folder into the system include directory

# CppUnit tests

# ... find cppunit include and library, if it exists

find_path(CPPUNIT_INCLUDE_DIR cppunit/TestRunner.h

        PATHS /usr/include /usr/local/include /opt/local/include

)

find_library(CPPUNIT_LIBRARY cppunit

        PATHS /usr/lib /usr/local/lib /opt/local/lib

)

if (CPPUNIT_INCLUDE_DIR AND CPPUNIT_LIBRARY)

    message(STATUS "CppUnit found: Enabling unit and systemtests.")

    file(GLOB TEST_SOURCES ${UNIT_TESTS_DIR}/*.cpp) # detect test files

    add_executable(test_unit_runner ${TEST_SOURCES} ${TESTS_DIR}/TestRunner.cpp

            ${UNIT_TESTS_DIR}/AuxiliaryTest.cpp

            ${UNIT_TESTS_DIR}/BloomFilterSyncTest.cpp

            ${UNIT_TESTS_DIR}/BloomFilterTest.cpp

            ${UNIT_TESTS_DIR}/CommSocketTest.cpp

            ${UNIT_TESTS_DIR}/CommStringTest.cpp

            ${UNIT_TESTS_DIR}/CommunicantTest.cpp

            ${UNIT_TESTS_DIR}/Compact2DBitArrayTest.cpp

            ${UNIT_TESTS_DIR}/CPISyncTest.cpp

            ${UNIT_TESTS_DIR}/CuckooSyncTest.cpp

            ${UNIT_TESTS_DIR}/CuckooTest.cpp

            ${UNIT_TESTS_DIR}/DataObjectTest.cpp

            ${UNIT_TESTS_DIR}/DataPriorityObjectTest.cpp

            ${UNIT_TESTS_DIR}/FullSyncTest.cpp

            ${UNIT_TESTS_DIR}/IBLTSetOfSetsTest.cpp

            ${UNIT_TESTS_DIR}/CPISyncTest.cpp

    )

    target_include_directories(test_unit_runner PRIVATE ${TESTS_DIR} ${UNIT_TESTS_DIR}/include)

    target_link_libraries(test_unit_runner gensync ntl cppunit pthread gmp)

    add_executable(test_sys_runner ${TEST_SOURCES} ${TESTS_DIR}/TestRunner.cpp

            ${SYS_TESTS_DIR}/benchmark/BenchmarkTest.cpp

            ${SYS_TESTS_DIR}/long/GenericSyncTests.cpp

    )

    target_include_directories(test_sys_runner PRIVATE ${TESTS_DIR} ${UNIT_TESTS_DIR}/include)

    target_link_libraries(test_sys_runner gensync ntl cppunit pthread gmp)

    enable_testing()

    add_test(NAME UnitTests COMMAND test_unit_runner)

    add_test(NAME SystemTests COMMAND test_sys_runner)

else()

    message(WARNING "CppUnit NOT found.  Skipping unit tests.")

endif()

    #Packaging

set(CPACK_GENERATOR "RPM;DEB")

set(CPACK_PACKAGE_VERSION ${VERSION})

set(CPACK_PACKAGE_DESCRIPTION_SUMMARY "A library for remote file synchronization research")

set(CPACK_PACKAGE_DESCRIPTION_FILE ${CMAKE_SOURCE_DIR}/README.md)

set(CPACK_RESOURCE_FILE_LICENSE ${CMAKE_SOURCE_DIR}/LICENSE)

set(CPACK_PACKAGE_NAME "GenSync")

set(CPACK_PACKAGE_VERSION_MAJOR "2")

set(CPACK_PACKAGE_VERSION_MINOR "0")

set(CPACK_PACKAGE_VERSION_PATCH "5")

set(CPACK_PACKAGE_CONTACT "Ari Trachtenberg")

set(CPACK_PACKAGE_VENDOR "NISLAB")

set(CPACK_PACKAGING_INSTALL_PREFIX ${CMAKE_INSTALL_PREFIX})

set(CPACK_PACKAGE_FILE_NAME "${CPACK_PACKAGE_NAME}-${CPACK_PACKAGE_VERSION_MAJOR}.${CPACK_PACKAGE_VERSION_MINOR}.${CPACK_PACKAGE_VERSION_PATCH}-${CPACK_PACKAGE_RELEASE}.${CMAKE_SYSTEM_PROCESSOR}")

set(CPACK_RPM_EXCLUDE_FROM_AUTO_FILELIST /opt/local /opt/local/lib /opt/local/include)

include(CPack)

# Problem Zero

## Getting started

To make it easy for you to get started with GitLab, here's a list of recommended next steps.

Already a pro? Just edit this README.md and make it your own. Want to make it easy? [Use the template at the bottom](#editing-this-readme)!

## Add your files

- [ ] [Create](https://docs.gitlab.com/ee/user/project/repository/web_editor.html#create-a-file) or [upload](https://docs.gitlab.com/ee/user/project/repository/web_editor.html#upload-a-file) files

- [ ] [Add files using the command line](https://docs.gitlab.com/ee/gitlab-basics/add-file.html#add-a-file-using-the-command-line) or push an existing Git repository with the following command:

```

cd existing_repo

git remote add origin https://agile.bu.edu/gitlab/ec531/homeworks/problems/hw2/p0.git

git branch -M master

git push -uf origin master

```

## Integrate with your tools

- [ ] [Set up project integrations](https://agile.bu.edu/gitlab/ec531/homeworks/problems/hw2/p0/-/settings/integrations)

## Collaborate with your team

- [ ] [Invite team members and collaborators](https://docs.gitlab.com/ee/user/project/members/)

- [ ] [Create a new merge request](https://docs.gitlab.com/ee/user/project/merge_requests/creating_merge_requests.html)

- [ ] [Automatically close issues from merge requests](https://docs.gitlab.com/ee/user/project/issues/managing_issues.html#closing-issues-automatically)

- [ ] [Enable merge request approvals](https://docs.gitlab.com/ee/user/project/merge_requests/approvals/)

- [ ] [Set auto-merge](https://docs.gitlab.com/ee/user/project/merge_requests/merge_when_pipeline_succeeds.html)

## Test and Deploy

Use the built-in continuous integration in GitLab.

- [ ] [Get started with GitLab CI/CD](https://docs.gitlab.com/ee/ci/quick_start/index.html)

- [ ] [Analyze your code for known vulnerabilities with Static Application Security Testing (SAST)](https://docs.gitlab.com/ee/user/application_security/sast/)

- [ ] [Deploy to Kubernetes, Amazon EC2, or Amazon ECS using Auto Deploy](https://docs.gitlab.com/ee/topics/autodevops/requirements.html)

- [ ] [Use pull-based deployments for improved Kubernetes management](https://docs.gitlab.com/ee/user/clusters/agent/)

- [ ] [Set up protected environments](https://docs.gitlab.com/ee/ci/environments/protected_environments.html)

***

# Editing this README

When you're ready to make this README your own, just edit this file and use the handy template below (or feel free to structure it however you want - this is just a starting point!). Thanks to [makeareadme.com](https://www.makeareadme.com/) for this template.

## Suggestions for a good README

Every project is different, so consider which of these sections apply to yours. The sections used in the template are suggestions for most open source projects. Also keep in mind that while a README can be too long and detailed, too long is better than too short. If you think your README is too long, consider utilizing another form of documentation rather than cutting out information.

## Name

Choose a self-explaining name for your project.

## Description

Let people know what your project can do specifically. Provide context and add a link to any reference visitors might be unfamiliar with. A list of Features or a Background subsection can also be added here. If there are alternatives to your project, this is a good place to list differentiating factors.

## Badges

On some READMEs, you may see small images that convey metadata, such as whether or not all the tests are passing for the project. You can use Shields to add some to your README. Many services also have instructions for adding a badge.

## Visuals

Depending on what you are making, it can be a good idea to include screenshots or even a video (you'll frequently see GIFs rather than actual videos). Tools like ttygif can help, but check out Asciinema for a more sophisticated method.

## Installation

Within a particular ecosystem, there may be a common way of installing things, such as using Yarn, NuGet, or Homebrew. However, consider the possibility that whoever is reading your README is a novice and would like more guidance. Listing specific steps helps remove ambiguity and gets people to using your project as quickly as possible. If it only runs in a specific context like a particular programming language version or operating system or has dependencies that have to be installed manually, also add a Requirements subsection.

## Usage

Use examples liberally, and show the expected output if you can. It's helpful to have inline the smallest example of usage that you can demonstrate, while providing links to more sophisticated examples if they are too long to reasonably include in the README.

## Support

Tell people where they can go to for help. It can be any combination of an issue tracker, a chat room, an email address, etc.

## Roadmap

If you have ideas for releases in the future, it is a good idea to list them in the README.

## Contributing

State if you are open to contributions and what your requirements are for accepting them.

For people who want to make changes to your project, it's helpful to have some documentation on how to get started. Perhaps there is a script that they should run or some environment variables that they need to set. Make these steps explicit. These instructions could also be useful to your future self.

You can also document commands to lint the code or run tests. These steps help to ensure high code quality and reduce the likelihood that the changes inadvertently break something. Having instructions for running tests is especially helpful if it requires external setup, such as starting a Selenium server for testing in a browser.

## Authors and acknowledgment

Show your appreciation to those who have contributed to the project.

## License

For open source projects, say how it is licensed.

## Project status

If you have run out of energy or time for your project, put a note at the top of the README saying that development has slowed down or stopped completely. Someone may choose to fork your project or volunteer to step in as a maintainer or owner, allowing your project to keep going. You can also make an explicit request for maintainers.

BasedOnStyle: LLVM

IndentWidth: 4

name: C/C++ CI

on: 

  push:

    branches: 

      - master

  pull_request:

    branches: 

      - master

  schedule:

    - cron: "0 5 * * 0-6"

jobs:

  build:

    runs-on: ubuntu-latest

    steps:

    - uses: actions/checkout@v2

    - name: Cmake

      run: cmake .

    - name: Install Dependencies

      run: |

        sudo apt install cmake libgmp3-dev libcppunit-dev libpthread-stubs0-dev

        curl -O https://www.shoup.net/ntl/ntl-11.4.3.tar.gz

        tar -xzf ntl-11.4.3.tar.gz

        cd ntl-11.4.3/src

        ./configure 

        make -j 8

        sudo make install

    - name: make

      run: make -j 8

    - name: Unit Test

      run: ./UnitTest

    - name: System Long Test

      run: ./SystemLongTest