The -i allows stdin of your host machine to be passed into Docker to allow duplo to read the filenames. The working directory in the duplo container should be /src (that's where the duplo executable is located) and the current path of your host machine will be mapped to /src when the container is running. That is a good thing to do anyway, since it opens up a lot of possibilities apart from running duplo.Īgain, similarly to the Bash command, this uses find to find files in the current directory, then passes the file list to Docker which will pass it further into an instance of the latest version of duplo. #DUPLICATE FILE FINDER OPEN SOURCE INSTALL#You will have to install Docker though, if you haven't already. This is very convenient as you do not have to install duplo separately. This command also works in a similar fashion to the Bash command, but instead of piping into a local duplo executable, it will pipe into duplo running inside Docker. type f \( -iname "*.cpp " -or -iname "*.h " \) | docker run -rm -i -w /src -v $(pwd ):/src dlidstrom/duplo - out.txt In arbitrary text files and will even detect (without special support) duplicates detector In addition, Duplo can be used as a general Statements, etc, to only consider duplicates Preprocessor directives, block comments, using Ammann and is now maintained and developed by Danielĭuplo has built in support for the following Maintainerĭuplo was originally developed by Christian Programming languages, meaning it can filter out (multi-line) comments and compiler directives.įor example: C, C , Java, C#, and VB.NET. Duplo (C/C /Java Duplicate Source Code Block Finder)ĭuplicated source code blocks can harm maintainability of software systems.ĭuplo is a tool to find duplicated code blocks in large code bases.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |